Communication device

ABSTRACT

The communication device which implements a voice communicating function, an attached file emailing function, a geographic location function, a dictionary function, a schedule notifying function, a multiple type TV program function, a multiple TV screen displaying function, a touch panel function, a communication device finding function, and a resume enabled video game function, independently or simultaneously.

Paragraph [0001]—CROSS REFERENCE TO RELATED APPLICATIONS

Paragraph [0002]—The application is a continuation of U.S. Ser. No.11/623,061, filed 2007-Jan.-13, which is a continuation of U.S. Ser. No.10/905,365, filed 2004-Dec.-30, now abandoned which claims the benefitof U.S. Provisional Application No. 60/521,265, filed 2004-Mar.-23, allof which are hereby incorporated herein by reference in their entirety.

Paragraph [0003]—BACKGROUND OF INVENTION

Paragraph [0003.1]—The invention relates to a communication device andmore particularly to the communication device which has a capability tocommunicate with another communication device in a wireless fashion.

Paragraph [0004]—U.S. Pat. No. 4,937,570 is introduced as a prior art ofthe present invention of which the summary is the following: “A routeguidance display device for an automotive vehicle capable of displayingroute patterns with a three-dimensional effect to enhance the viewer'scomprehension of the road route situation being encountered. The displaydevice includes a plurality of intersecting display segments indicativeof corresponding possible route configurations. A depth-enhancingsegment is included in a portion indicating the straight-ahead route. Anintersection name display section may be separately included to displaythe name and related information regarding an intersection layingahead.” However, the foregoing prior art does not disclose thecommunication device which implements a voice communicating function, anattached file emailing function, a geographic location function, adictionary function, a schedule notifying function, a multiple type TVprogram function, a multiple TV screen displaying function, a touchpanel function, a communication device finding function, and a resumeenabled video game function, independently or simultaneously.

Paragraph [0005]—For the avoidance of doubt, the number of the priorarts introduced herein (and/or in IDS) may be of a large one, however,the applicant has no intent to hide the more relevant prior art(s) inthe less relevant ones.

Paragraph [0006]—SUMMARY OF INVENTION

Paragraph [0007]—It is an object of the present invention to provide adevice capable of implementing a plurality of functions.

Paragraph [0008]—It is another object of the present invention toprovide merchandise to merchants attractive to the consumers in the U.S.

Paragraph [0009]—It is another object of the present invention toprovide mobility to the users of the device in which the presentinvention is incorporated.

Paragraph [0010]—It is another object of the present invention toprovide more convenience to the users of the device compared to theprior art.

Paragraph [0011]—It is another object of the present invention toovercome the shortcomings associated with the prior art.

Paragraph [0012]—It is another object of the present invention toprovide a convenient device capable to implement the functions of bothvoice communication and audio(visual) player to consumers.

Paragraph [0013]—The present invention introduces the communicationdevice which implements a voice communicating function, an attached fileemailing function, a geographic location function, a dictionaryfunction, a schedule notifying function, a multiple type TV programfunction, a multiple TV screen displaying function, a touch panelfunction, a communication device finding function, and a resume enabledvideo game function, independently or simultaneously.

Paragraph [0014]—BRIEF DESCRIPTION OF DRAWING

Paragraph [0015]—The above and other aspects, features, and advantagesof the invention will be better understood by reading the following moreparticular description of the invention, presented in conjunction withthe following drawing, wherein:

Paragraph [0016]—FIG. 1 is a block diagram illustrating an exemplaryembodiment of the present invention.

Paragraph [0017]—DETAILED DESCRIPTION

Paragraph [0018]—The following description is of the best presentlycontemplated mode of carrying out the present invention. Thisdescription is not to be taken in a limiting sense but is made merelyfor the purpose of describing the general principles of the invention.For example, each description of random access memory in thisspecification illustrate(s) only one function or mode in order to avoidcomplexity in its explanation, however, such description does not meanthat only one function or mode can be implemented at a time. In otherwords, more than one function or mode can be implemented simultaneouslyby way of utilizing the same random access memory. In addition, theparagraph number is cited after the elements in parenthesis in a mannerfor example ‘RAM 206 (FIG. 1)’. It is done so merely to assist thereaders to have a better understanding of this specification, and mustnot be used to limit the scope of the claims in any manner since thefigure numbers cited are not exclusive. There are only few data storedin each storage area described in this specification. This is done somerely to simplify the explanation and, thereby, to enable the reader ofthis specification to understand the content of each function with lessconfusion. Therefore, more than few data (hundreds and thousands ofdata, if necessary) of the same kind, not to mention, are preferred tobe stored in each storage area to fully implement each functiondescribed herein. The scope of the invention should be determined byreferencing the appended claims.

Paragraph [0019]—FIG. 1 is a simplified block diagram of theCommunication Device 200 utilized in the present invention. Referring toFIG. 1, Communication Device 200 includes CPU 211 which controls andadministers the overall function and operation of Communication Device200. CPU 211 uses RAM 206 to temporarily store data and/or to performcalculation to perform its function, and to implement the presentinvention, modes, functions, and systems explained hereinafter. VideoProcessor 202 generates analog and/or digital video signals which aredisplayed on LCD 201. ROM 207 stores the data and programs which areessential to operate Communication Device 200. Wireless signals arereceived by Antenna 218 and processed by Signal Processor 208. Inputsignals are input by Input Device 210, such as a dial pad, a joystick,and/or a keypad, and the signals are transferred via Input Interface 209and Data Bus 203 to CPU 211. Indicator 212 is an LED lamp which isdesigned to output different colors (e.g., red, blue, green, etc).Analog audio data is input to Microphone 215. A/D 213 converts theanalog audio data into a digital format. Speaker 216 outputs analogaudio data which is converted into an analog format from digital formatby D/A 204. Sound Processor 205 produces digital audio signals that aretransferred to D/A 204 and also processes the digital audio signalstransferred from A/D 213. CCD Unit 214 captures video image which isstored in RAM 206 in a digital format. Vibrator 217 vibrates the entiredevice by the command from CPU 211.

Paragraph [0020]—As another embodiment, LCD 201 or LCD 201/VideoProcessor 202 may be separated from the other elements described in FIG.1, and be connected in a wireless fashion to be wearable and/orhead-mountable.

Paragraph [0021]—When Communication Device 200 is in the voicecommunication mode, the analog audio data input to Microphone 215 isconverted to a digital format by A/D 213 and transmitted to anotherdevice via Antenna 218 in a wireless fashion after being processed bySignal Processor 208, and the wireless signal representing audio datawhich is received via Antenna 218 is output from Speaker 216 after beingprocessed by Signal Processor 208 and converted to analog signal by D/A204. For the avoidance of doubt, the definition of Communication Device200 in this specification includes so-called ‘PDA’. The definition ofCommunication Device 200 also includes in this specification any devicewhich is mobile and/or portable and which is capable to send and/orreceive audio data, text data, image data, video data, and/or othertypes of data in a wireless fashion via Antenna 218. The definition ofCommunication Device 200 further includes any micro device embedded orinstalled into devices and equipments (e.g., VCR, TV, tape recorder,heater, air conditioner, fan, clock, micro wave oven, dish washer,refrigerator, oven, washing machine, dryer, door, window, automobile,motorcycle, and modem) to remotely control these devices and equipments.The size of Communication Device 200 is irrelevant. Communication Device200 may be installed in houses, buildings, bridges, boats, ships,submarines, airplanes, and spaceships, and firmly fixed therein.

Paragraph [0022]—Paragraph [0022] illustrate(s) the data stored in HostH. As described in Paragraph [0022], Host H includes Host InformationStorage Area H00a which stores various types of data to assist and/orco-operate with Communication Device 200 to implement all modes,functions, and systems described in this specification. As anotherembodiment, Host H may be composed of a plurality of computers, i.e.,one master computer and a plurality of slave computers, wherein themaster computer is connected to the plurality of slave computers. Asanother embodiment, Host H may also be composed of a plurality of mastercomputers by way of utilizing peer-to-peer connection.

Paragraph [0023]—<<Movie eTicket Function>>

Paragraph [0024]—This Paragraph [0024] through Paragraph [0070]illustrate(s) the movie eticket function which enables the user ofCommunication Device 200 to purchase the movie tickets via CommunicationDevice 200 and enter the movie theaters by utilizing CommunicationDevice 200 without utilizing paper tickets.

Paragraph [0025]—This Paragraph [0025] illustrate(s) the storage areaincluded in Host H (Paragraph [0022]). In the present embodiment, Host Hincludes Movie eTicket Data Storage Area H79b of which the data and thesoftware programs stored therein are described in Paragraph [0024].

Paragraph [0026]—This Paragraph [0026] illustrate(s) the storage areasincluded in Movie eTicket Data Storage Area H79b (Paragraph [0025]). Inthe present embodiment, Movie eTicket Data Storage Area H79b includesMovie Data Storage Area H79b1, User Data Storage Area H79b2, PurchaseData Storage Area H79b3, and Work Area H79b4. Movie Data Storage AreaH79b1 stores the data described in Paragraph [0027]. User Data StorageArea H79b2 stores the data described in Paragraph [0028]. Purchase DataStorage Area H79b3 stores the data described in Paragraph [0029]. WorkArea H79b4 is utilized as a work area to perform calculation andtemporarily store data.

Paragraph [0027]—This Paragraph [0027] illustrate(s) the data stored inMovie Data Storage Area H79b1 (Paragraph [0026]). In the presentembodiment, Movie Data Storage Area H79b1 comprises two columns, i.e.,‘Movie ID’ and ‘Movie Data’. Column ‘Movie ID’ stores the movie IDs, andeach movie ID is an identification of the corresponding movie datastored in column ‘Movie Data’. Column ‘Movie Data’ stores the moviedata, and each the movie data includes five types of data, i.e., title,location, starting time, ending time, and summary. Here, the titlerepresents the title of the movie represented by the corresponding movieID, the location represents the geographic location of theater where themovie represented by the corresponding movie ID is shown, the startingtime represents the starting time of the movie represented by thecorresponding movie ID, the ending time represents the ending time ofthe movie represented by the corresponding movie ID, and the summaryrepresents the summary of the movie represented by the correspondingmovie ID. In the present embodiment, Movie Data Storage Area H79b1stores the following data: the movie ID ‘Movie#1’ and the correspondingmovie data ‘Movie Data#1 (Title#1, Location#1, Starting Time#1, EndingTime#1, Summary#1)’; the movie ID ‘Movie#2’ and the corresponding moviedata ‘Movie Data#2 (Title#2, Location#2, Starting Time#2, Ending Time#2,Summary#2)’; the movie ID ‘Movie#3’ and the corresponding movie data‘Movie Data#3 (Title#3, Location#3, Starting Time#3, Ending Time#3,Summary#3)’; and the movie ID ‘Movie#4’ and the corresponding movie data‘Movie Data#4 (Title#4, Location#4, Starting Time#4, Ending Time#4,Summary#4)’.

Paragraph [0028]—This Paragraph [0028] illustrate(s) the data stored inUser Data Storage Area H79b2 (Paragraph [0026]). In the presentembodiment, User Data Storage Area H79b2 comprises two columns, i.e.,‘User ID’ and ‘User Data’. Column ‘User ID’ stores the user IDs, andeach user ID is an identification of the user data stored in column‘User Data’. Column ‘User Data’ stores the user data, and each user dataincludes name, home address, phone number, email address, and creditcard information. Here, the name represents the name of the user ofCommunication Device 200, the home address represents the home addressof the user, the phone number represents the phone number of the user,the email address represents the email address of the user, and thecredit card information represents the credit card information of theuser. In the present embodiment, User Data Storage Area H79b2 stores thefollowing data: the user ID ‘User#1’ and the user data ‘User Data#1(Name#1, Home Address#1, Phone Number#1, Email Address#1, Credit CardInformation#1)’; the user ID ‘User#2’ and the user data ‘User Data#2(Name#2, Home Address#2, Phone Number#2, Email Address#2, Credit CardInformation#2)’; the user ID ‘User#3’ and the user data ‘User Data#3(Name#3, Home Address#3, Phone Number#3, Email Address#3, Credit CardInformation#3)’; and the user ID ‘User#4’ and the user data ‘User Data#4(Name#4, Home Address#4, Phone Number#4, Email Address#4, Credit CardInformation#4)’.

Paragraph [0029]—This Paragraph [0029] illustrate(s) the data stored inPurchase Data Storage Area H79b3 (Paragraph [0026]). In the presentembodiment, Purchase Data Storage Area H79b3 comprises two columns,i.e., ‘User ID’ and ‘Purchase Data’. Column ‘User ID’ stores the userIDs described in Paragraph [0028]. Column ‘Purchase Data’ stores thepurchase data, and each purchase data is composed of alphanumeric datawhich do not represent or indicate the user data. A unique alphanumericdata may be assigned to each purchase data so that each purchase data isdistinguished from the other purchase data. In the present embodiment,Purchase Data Storage Area H79b3 stores the following data: the user ID‘User#1’ and the corresponding purchase data ‘Purchase Data#1’; the userID ‘User#2’ and the corresponding purchase data ‘Purchase Data#2’; theuser ID ‘User#3’ and the corresponding purchase data ‘Purchase Data#3’;and the user ID ‘User#4’ and the corresponding purchase data ‘PurchaseData#4’. As another embodiment, a common alphanumeric data may beassigned to all purchase data (i.e., Purchase Data#1, Purchase Data#2,Purchase Data#3, and Purchase Data#4 are composed of the samealphanumeric data).

Paragraph [0030]—This Paragraph [0030] illustrate(s) the softwareprograms stored in Movie eTicket Software Storage Area H79c (Paragraph[0025]). In the present embodiment, Movie eTicket Software Storage AreaH79c stores Movie Data Selecting Software H79c1, Purchase Data ProducingSoftware H79c2, Purchase Data Updating Software H79c3, Purchase DataDeleting Software H79c5, and Movie eTicket Information Storage Area20679a. Movie Data Selecting Software H79c1 is the software programdescribed in Paragraph [0039]. Purchase Data Producing Software H79c2 isthe software program described in Paragraph [0040]. Purchase DataUpdating Software H79c3 is the software program described in Paragraph[0047]. Purchase Data Deleting Software H79c5 is the software programdescribed in Paragraph [0049].

Paragraph [0031]—This Paragraph [0031] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Communication Device 200. In the presentembodiment, RAM 206 includes Movie eTicket Information Storage Area20679a of which the data and the software programs stored therein aredescribed in Paragraph [0033].

Paragraph [0032]—The data and/or the software programs stored in MovieeTicket Information Storage Area 20679a (Paragraph [0031]) may bedownloaded from Host H (Paragraph [0022]) in the manner described inParagraph [0416] through Paragraph [0422].

Paragraph [0033]—This Paragraph [0033] illustrate(s) the storage areasincluded in Movie eTicket Information Storage Area 20679a (Paragraph[0031]). In the present embodiment, Movie eTicket Information StorageArea 20679a includes Movie eTicket Data Storage Area 20679b and MovieeTicket Software Storage Area 20679c. Movie eTicket Data Storage Area20679b stores the data described in Paragraph [0034] through Paragraph[0037]. Movie eTicket Software Storage Area 20679c stores the datadescribed in Paragraph [0038].

Paragraph [0034]—This Paragraph [0034] illustrate(s) the storage areasincluded in Movie eTicket Data Storage Area 20679b (Paragraph [0033]).In the present embodiment, Movie eTicket Data Storage Area 20679bincludes Movie Data Storage Area 20679b1, User Data Storage Area20679b2, Purchase Data Storage Area 20679b3, and Work Area 20679b4.Movie Data Storage Area 20679b1 stores the data described in Paragraph[0035]. User Data Storage Area 20679b2 stores the data described inParagraph [0036]. Purchase Data Storage Area 20679b3 stores the datadescribed in Paragraph [0037]. Work Area 20679b4 is utilized as a workarea to perform calculation and temporarily store data.

Paragraph [0035]—This Paragraph [0035] illustrate(s) the data stored inMovie Data Storage Area 20679b1 (Paragraph [0034]). In the presentembodiment, Movie Data Storage Area 20679b1 comprises two columns, i.e.,‘Movie ID’ and ‘Movie Data’. Column ‘Movie ID’ stores the movie IDs, andeach movie ID is an identification of the corresponding movie datastored in column ‘Movie Data’. Column ‘Movie Data’ stores the moviedata, and each the movie data includes five types of data, i.e., title,location, starting time, ending time, and summary. Here, the titlerepresents the title of the movie represented by the corresponding movieID, the location represents the geographic location of theater where themovie represented by the corresponding movie ID is shown, the startingtime represents the starting time of the movie represented by thecorresponding movie ID, the ending time represents the ending time ofthe movie represented by the corresponding movie ID, and the summaryrepresents the summary of the movie represented by the correspondingmovie ID. In the present embodiment, Movie Data Storage Area H79b1stores the following data: the movie ID ‘Movie#1’ and the correspondingmovie data ‘Movie Data#1 (Title#1, Location#1, Starting Time#1, EndingTime#1, Summary#1)’; the movie ID ‘Movie#2’ and the corresponding moviedata ‘Movie Data#2 (Title#2, Location#2, Starting Time#2, Ending Time#2,Summary#2)’; the movie ID ‘Movie#3’ and the corresponding movie data‘Movie Data#3 (Title#3, Location#3, Starting Time#3, Ending Time#3,Summary#3)’; and the movie ID ‘Movie#4’ and the corresponding movie data‘Movie Data#4 (Title#4, Location#4, Starting Time#4, Ending Time#4,Summary#4)’.

Paragraph [0036]—This Paragraph [0036] illustrate(s) the data stored inUser Data Storage Area 20679b2 (Paragraph [0034]). In the presentembodiment, User Data Storage Area 20679b2 comprises two columns, i.e.,‘User ID’ and ‘User Data’. Column ‘User ID’ stores the user ID which isan identification of the user data stored in column ‘User Data’. Column‘User Data’ stores the user data which includes name, home address,phone number, email address, and credit card information. Here, the namerepresents the name of the user of Communication Device 200 (e.g.,device A), the home address represents the home address of the user, thephone number represents the phone number of the user, the email addressrepresents the email address of the user, and the credit cardinformation represents the credit card information of the user. In thepresent embodiment, User Data Storage Area 20679b2 stores the followingdata: the user ID ‘User#4’ and the user data ‘User Data#4 (Name#4, HomeAddress#4, Phone Number#4, Email Address#4, Credit Card Information#4)’.

Paragraph [0037]—This Paragraph [0037] illustrate(s) the data stored inPurchase Data Storage Area 20679b3 (Paragraph [0034]). In the presentembodiment, Purchase Data Storage Area 20679b3 comprises two columns,i.e., ‘User ID’ and Purchase Data'. Column ‘User ID’ stores the user IDsdescribed in Paragraph [0036]. Column ‘Purchase Data’ stores thepurchase data which is composed of alphanumeric data which do notrepresent or indicate the user data. In the present embodiment, PurchaseData Storage Area 20679b3 stores the following data: the user ID‘User#4’ and the corresponding purchase data ‘Purchase Data#4’.

Paragraph [0038]—This Paragraph [0038] illustrate(s) the softwareprograms stored in Movie eTicket Software Storage Area 20679c (Paragraph[0033]). In the present embodiment, Movie eTicket Software Storage Area20679c stores Movie Data Selecting Software 20679c1, Purchase DataProducing Software 20679c2, and purchase data Authenticating Software20679c4. Movie Data Selecting Software 20679c1 is the software programdescribed in Paragraph [0039]. Purchase Data Producing Software 20679c2is the software program described in Paragraph [0040]. Purchase DataAuthenticating Software 20679c4 is the software program described inParagraph [0048].

Paragraph [0039]—This Paragraph [0039] illustrate(s) Movie DataSelecting Software H79c1 (Paragraph [0030]) of Host H (Paragraph [0022])and Movie Data Selecting Software 20679c1 (Paragraph [0038]) ofCommunication Device 200, which selects a movie for which the movieeticket is to be purchased. In the present embodiment, Host H retrievesall movie IDs and movie data from Movie Data Storage Area H79b1(Paragraph [0027]), and sends these data to Communication Device 200 ina wireless fashion (S1). Upon receiving the movie IDs and the movie datafrom Host H, CPU 211 (FIG. 1) of Communication Device 200 stores thesedata in Movie Data Storage Area 20679b1 (Paragraph [0035]) (S2). CPU 211retrieves the movie data from Movie Data Storage Area 20679b1 (Paragraph[0035]) and displays a movie list on LCD 201 (FIG. 1) (S3). The user ofCommunication Device 200 selects a movie data (e.g., Movie Data#1) byutilizing Input Device 210 (FIG. 1) or via voice recognition system(S4).

Paragraph [0040]—This Paragraph [0040] illustrate(s) Purchase DataProducing Software H79c2 (Paragraph [0030]) of Host H (Paragraph [0022])and Purchase Data Producing Software 20679c2 (Paragraph [0038]) ofCommunication Device 200, which produces a purchase data. In the presentembodiment, CPU 211 (FIG. 1) of Communication Device 200 retrieves itsuser data (e.g., User Data#4) from User Data Storage Area 20679b2(Paragraph [0036]) (S1), and sends in a wireless fashion thecorresponding movie ID (e.g., Movie#1) of the movie data selected in S4(e.g., Movie Data#1) and the user data (e.g., User Data#4), which arereceived by Host H (S2). Host H retrieves the credit card information(e.g., Credit Card Information#4) from the user data (e.g., UserData#4), and performs the credit card authentication process which is aprocess to authenticate the credit card information (e.g., Credit CardInformation#4) (S3). If the credit card information is authenticated,Host H produces a new user ID (e.g., User#4) and stores the user data(e.g., User Data#4) at the corresponding user ID (e.g., User#4) in UserData Storage Area H79b2 (Paragraph [0028]) (S4). Host H produces apurchase data (e.g., Purchase Data#4) and stores the data at thecorresponding user ID (e.g., User#4) in Purchase Data Storage Area H79b3(Paragraph [0029]) (S5). Host H sends in a wireless fashion the purchasedata (e.g., Purchase Data#4), and Communication Device 200 receives thedata (S6). CPU 211 of Communication Device 200 stores the purchase data(e.g., Purchase Data#4) in Purchase Data Storage Area 20679b3 (Paragraph[0037]) (S7).

Paragraph [0041]—This Paragraph [0041] illustrate(s) the function ofMovie eTicket Authenticating Device MAD79, Admission Gate ControllerAGC79, and Admission Gate AG79. In the present embodiment, Movie eTicketAuthenticating Device MAD79 is connected to Admission Gate ControllerAGC79, and Admission Gate Controller AGC79 is connected to AdmissionGate AG79 Admission Gate AG79 is the gate installed at the entrance of amovie theater. Admission Gate AG79 is normally closed, and opens onlywhen an admission gate signal is sent from Admission Gate ControllerAGC79. People are able to go through Admission Gate AG79 when it isopen. Admission Gate Controller AGC79 is a device to control AdmissionGate AG79. Admission Gate Controller AGC79 sends the admission gatesignal which is a command to open the gate of Admission Gate AG79. Theadmission gate signal is sent when Admission Gate Controller AGC79receives an admission signal sent from Movie eTicket AuthenticatingDevice MAD79. Here, the admission signal is a signal which indicatesthat a movie eticket is authenticated of which the process therefor isexplained hereinafter.

Paragraph [0042]—This Paragraph [0042] illustrate(s) the storage areasincluded in Movie eTicket Authenticating Device MAD79a (Paragraph[0041]). In the present embodiment, Movie eTicket Authenticating DeviceMAD79a includes Authenticated Movie eTicket Data Storage Area MAD79b andAuthenticated Movie eTicket Software Storage Area MAD79c. AuthenticatedMovie eTicket Data Storage Area MAD79b stores the data necessary toimplement the present function, such as the ones described in Paragraph[0043] and Paragraph [0045]. Authenticated Movie eTicket SoftwareStorage Area MAD79c stores the software programs necessary to implementthe present function, such as the ones described in Paragraph [0046].

Paragraph [0043]—This Paragraph [0043] illustrate(s) the storage areasincluded in Authenticated Movie eTicket Data Storage Area MAD79b(Paragraph [0042]). In the present embodiment, Authenticated MovieeTicket Data Storage Area MAD79b includes Purchase Data Storage AreaMAD79b1, User Data Storage Area MAD79b2, and Work Area MAD79b3. PurchaseData Storage Area MAD79b1 stores the data described in Paragraph [0045].User Data Storage Area MAD79b2 stores the data described in Paragraph[0044]. Work Area MAD79b3 is utilized as a work area to performcalculation and temporarily store data.

Paragraph [0044]—This Paragraph [0044] illustrate(s) the data stored inUser Data Storage Area MAD79b2 (Paragraph [0043]). In the presentembodiment, User Data Storage Area MAD79b2 comprises two columns, i.e.,‘User ID’ and ‘User Data’. Column ‘User ID’ stores the user IDs, andeach user ID is an identification of the corresponding user data storedin column ‘User Data’. Column ‘User Data’ stores the user data, and eachuser data includes name, home address, phone number, email address, andcredit card information. Here, the name represents the name of thecorresponding user of Communication Device 200, the home addressrepresents the home address of the corresponding user, the phone numberrepresents the phone number of the corresponding user, the email addressrepresents the email address of the corresponding user, and the creditcard information represents the credit card information of thecorresponding user. In the present embodiment, User Data Storage AreaMAD79b2 stores the following data: the user ID ‘User#1’ and thecorresponding user data ‘User Data#1 (Name#1, Home Address#1, PhoneNumber#1, Email Address#1, Credit Card Information#1)’; the user ID‘User#2’ and the corresponding user data ‘User Data#2 (Name#2, HomeAddress#2, Phone Number#2, Email Address#2, Credit Card Information#2)’;the user ID ‘User#3’ and the corresponding user data ‘User Data#3(Name#3, Home Address#3, Phone Number#3, Email Address#3, Credit CardInformation#3)’; and the user ID ‘User#4’ and the corresponding userdata ‘User Data#4 (Name#4, Home Address#4, Phone Number#4, EmailAddress#4, Credit Card Information#4)’.

Paragraph [0045]—This Paragraph [0045] illustrate(s) the data stored inPurchase Data Storage Area MAD79b1 (Paragraph [0043]). In the presentembodiment, Purchase Data Storage Area MAD79b1 comprises two columns,i.e., ‘User ID’ and ‘Purchase Data’. Column ‘User ID’ stores the user113 s described in Paragraph [0044]. Column ‘Purchase Data’ stores thepurchase data, and each purchase data is composed of alphanumeric datawhich do not represent or indicate the user data. A unique alphanumericdata may be assigned to each purchase data so that each purchase data isdistinguished from the other purchase data. In the present embodiment,Purchase Data Storage Area MAD79b1 stores the following data: the userID ‘User#1’ and the corresponding purchase data ‘Purchase Data#1’; theuser ID ‘User#2’ and the corresponding purchase data ‘Purchase Data#2’;the user ID ‘User#3’ and the corresponding purchase data ‘PurchaseData#3’; and the user ID ‘User#4’ and the corresponding purchase data‘Purchase Data#4’. As another embodiment, a common alphanumeric data maybe assigned to all purchase data (i.e., Purchase Data#1, PurchaseData#2, Purchase Data#3, and Purchase Data#4 are composed of the samealphanumeric data).

Paragraph [0046]—This Paragraph [0046] illustrate(s) the softwareprograms stored in Authenticated Movie eTicket Software Storage AreaMAD79c (Paragraph [0042]). In the present embodiment, AuthenticatedMovie eTicket Software Storage Area MAD79c stores Purchase Data UpdatingSoftware MAD79c3, Purchase Data Authenticating Software MAD79c4, andpurchase data Deleting Software MAD79c5. Purchase Data Updating SoftwareMAD79c3 is the software program described in Paragraph [0047]. PurchaseData Authenticating Software MAD79c4 is the software program describedin Paragraph [0048]. Purchase Data Deleting Software MAD79c5 is thesoftware program described in Paragraph [0049].

Paragraph [0047]—This Paragraph [0047] illustrate(s) Purchase DataUpdating Software H79c3 (Paragraph [0030]) of Host H (Paragraph [0022])and purchase data Updating Software MAD79c3 (Paragraph [0046]) of MovieeTicket Authenticating Device MAD79 (Paragraph [0041]), which update thepurchase data stored in Movie eTicket Authenticating Device MAD79(Paragraph [0041]). In the present embodiment, Host H retrieves all userIDs and purchase data from Purchase Data Storage Area H79b3 (Paragraph[0029]) and sends the data to Movie eTicket Authenticating Device MAD79(Paragraph [0041]) (S1). Movie eTicket Authenticating Device MAD79receives the user IDs and the purchase data from Host H and stores thedata in Purchase Data Storage Area MAD79b1 (Paragraph [0045]) (S2).

Paragraph [0048]—This Paragraph [0048] illustrate(s) Purchase DataAuthenticating Software MAD79c4 (Paragraph [0046]) of Movie eTicketAuthenticating Device MAD79 (Paragraph [0041]) and purchase dataAuthenticating Software 20679c4 (Paragraph [0038]) of CommunicationDevice 200, which authenticate the purchase data sent from CommunicationDevice 200. In the present embodiment, CPU 211 (FIG. 1) of CommunicationDevice 200 retrieves the purchase data (e.g., Purchase Data#4) fromPurchase Data Storage Area 20679b3 (Paragraph [0037]) and sends in awireless fashion the data to Movie eTicket Authenticating Device MAD79(Paragraph [0041]) (S1). Movie eTicket Authenticating Device MAD79(Paragraph [0041]) receives the purchase data (e.g., Purchase Data#4)from Communication Device 200 and stores the data in Work Area MAD79b3(Paragraph [0043]) (S2). Movie eTicket Authenticating Device MAD79performs the authentication process, i.e., scans Purchase Data StorageArea MAD79b1 (Paragraph [0045]) (S3). If the purchase data (e.g.,Purchase Data#4) is authenticated, Movie eTicket Authenticating DeviceMAD79 sends an admission signal to Admission Gate Controller AGC79(Paragraph [0041]) to open Admission Gate AG79 (Paragraph [0041]) (S4).Movie eTicket Authenticating Device MAD79 (Paragraph [0041]) sends in awireless fashion a purchase data granted signal, which is received byCommunication Device 200 (S5). Here, the purchase data granted signal isthe signal which indicates that the purchase data (e.g., PurchaseData#4) is authenticated and thereby the user of Communication Device200 is allowed to go through Admission Gate AG79 (Paragraph [0041]). CPU211 (FIG. 1) of Communication Device 200 stores the purchase datagranted signal in Work Area 20679b4 (Paragraph [0034]) (S6), anddisplays the purchase data granted notification data on LCD 201 (FIG. 1)(S7). Here, the purchase data granted notification data is an image datadesigned to be displayed on LCD 201 (FIG. 1) which indicates that thepurchase data (e.g., Purchase Data#4) is authenticated and thereby theuser of Communication Device 200 is allowed to go through Admission GateAG79 (Paragraph [0041]). If the movie theater has no Admission Gate AG79(Paragraph [0041]) or Admission Gate AG79 (Paragraph [0041]) is notfunctioning, the attendant of the movie theater may visually confirm thepurchase data granted notification displayed on LCD 201 (FIG. 1), andthereby allow the user of Communication Device 200 to enter the movietheater.

Paragraph [0049]—This Paragraph [0049] illustrate(s) Purchase DataDeleting Software H79c5 (Paragraph [0030]) of Host H (Paragraph [0022])and purchase data Deleting Software MAD79c5 (Paragraph [0046]) of MovieeTicket Authenticating Device MAD79 (Paragraph [0041]), which delete thepurchase data stored in Movie eTicket Authenticating Device MAD79(Paragraph [0041]). In the present embodiment, Movie eTicketAuthenticating Device MAD79 (Paragraph [0041]) sends a purchase dataexpiration signal, which is received by Host H (S1). Here, the purchasedata expiration signal is the signal which indicates that the user ofCommunication Device 200 has gone through Admission Gate AG79 (Paragraph[0041]) and, thereby, the purchase data (e.g., Purchase Data#4) is nolonger valid. In response to the purchase data expiration signal, Host Hdeletes the purchase data (e.g., Purchase Data#4) and the correspondinguser ID (e.g., User#4) stored in Purchase Data Storage Area H79b3(Paragraph [0029]) (S2). Host H also deletes the user ID (e.g., User#4)and the corresponding user data (e.g., User Data#4) stored in User DataStorage Area H79b2 (Paragraph [0028]) (S3).

Paragraph [0050]—<<Movie eTicket Function—Another Embodiment01>>

Paragraph [0051]—Paragraph [0052] through Paragraph [0058] illustrate(s)another embodiment of the present function wherein the user data,instead of the purchase data, is utilized for performing the admissionprocess.

Paragraph [0052]—This Paragraph [0052] illustrate(s) the softwareprograms stored in Movie eTicket Software Storage Area H79c (Paragraph[0025]). In the present embodiment, Movie eTicket Software Storage AreaH79c stores User Data Updating Software H79c3a and User Data DeletingSoftware H79c5a. User Data Updating Software H79c3a is the softwareprogram described in Paragraph [0056]. User Data Deleting SoftwareH79c5a is the software program described in Paragraph [0058].

Paragraph [0053]—This Paragraph [0053] illustrate(s) the softwareprograms stored in Movie eTicket Software Storage Area 20679c (Paragraph[0033]). In the present embodiment, Movie eTicket Software Storage Area20679c stores User Data Authenticating Software 20679c4a. User DataAuthenticating Software 20679c4a is the software program described inParagraph [0057].

Paragraph [0054]—This Paragraph [0054] illustrate(s) the data stored inUser Data Storage Area MAD79b2 (Paragraph [0043]). In the presentembodiment, User Data Storage Area MAD79b2 comprises two columns, i.e.,‘User ID’ and ‘User Data’. Column ‘User ID’ stores the user IDs, andeach user ID is an identification of the user data stored in column‘User Data’. Column ‘User Data’ stores the user data, and each user dataincludes name, home address, phone number, email address, and creditcard information. Here, the name represents the name of the user ofCommunication Device 200, the home address represents the home addressof the user, the phone number represents the phone number of the user,the email address represents the email address of the user, and thecredit card information represents the credit card information of theuser. In the present embodiment, User Data Storage Area MAD79b2 storesthe following data: the user ID ‘User#1’ and the user data ‘User Data#1(Name#1, Home Address#1, Phone Number#1, Email Address#1, Credit CardInformation#1)’; the user ID ‘User#2’ and the user data ‘User Data#2(Name#2, Home Address#2, Phone Number#2, Email Address#2, Credit CardInformation#2)’; the user ID ‘User#3’ and the user data ‘User Data#3(Name#3, Home Address#3, Phone Number#3, Email Address#3, Credit CardInformation#3)’; and the user ID ‘User#4’ and the user data ‘User Data#4(Name#4, Home Address#4, Phone Number#4, Email Address#4, Credit CardInformation#4)’.

Paragraph [0055]—This Paragraph [0055] illustrate(s) the softwareprograms stored in Authenticated Movie eTicket Software Storage AreaMAD79c (Paragraph [0042]). In the present embodiment, AuthenticatedMovie eTicket Software Storage Area MAD79c stores User Data UpdatingSoftware MAD79c3a, User Data Authenticating Software MAD79c4a, and UserData Deleting Software MAD79c5a. User Data Updating Software MAD79c3a isthe software program described in Paragraph [0056]. User DataAuthenticating Software MAD79c4a is the software program described inParagraph [0057]. User Data Deleting Software MAD79c5a is the softwareprogram described in Paragraph [0058].

Paragraph [0056]—This Paragraph [0056] illustrate(s) User Data UpdatingSoftware H79c3a (Paragraph [0030]) of Host H (Paragraph [0022]) and userdata Updating Software MAD79c3a (Paragraph [0046]) of Movie eTicketAuthenticating Device MAD79 (Paragraph [0041]), which update the userdata stored in Movie eTicket Authenticating Device MAD79 (Paragraph[0041]). In the present embodiment, Host H retrieves all user IDs anduser data from User Data Storage Area H79b2 (Paragraph [0028]) and sendsthe data to Movie eTicket Authenticating Device MAD79 (Paragraph [0041])(S1). Movie eTicket Authenticating Device MAD79 (Paragraph [0041])receives the user IDs and the user data from Host H and stores the datain User Data Storage Area MAD79b2 (Paragraph [0054]) (S2).

Paragraph [0057]—This Paragraph [0057] illustrate(s) User DataAuthenticating Software MAD79c4a (Paragraph [0046]) of Movie eTicketAuthenticating Device MAD79 (Paragraph [0041]) and User DataAuthenticating Software 20679c4a (Paragraph [0038]) of CommunicationDevice 200, which authenticate the user data sent from CommunicationDevice 200. In the present embodiment, CPU 211 (FIG. 1) of CommunicationDevice 200 retrieves its user data (e.g., User Data#4) from User DataStorage Area 20679b2 (Paragraph [0036]) and sends in a wireless fashionthe data to Movie eTicket Authenticating Device MAD79 (Paragraph [0041])(S1). Movie eTicket Authenticating Device MAD79 (Paragraph [0041])receives the user data (e.g., User Data#4) from Communication Device 200and stores the data in Work Area MAD79b3 (Paragraph [0043]) (S2). MovieeTicket Authenticating Device MAD79 (Paragraph [0041]) performs theauthentication process, i.e., scans User Data Storage Area MAD79b2(Paragraph [0054]) (S3). If the user data is authenticated, MovieeTicket Authenticating Device MAD79 (Paragraph [0041]) sends anadmission signal to Admission Gate Controller AGC79 (Paragraph [0041])to open Admission Gate AG79 (Paragraph [0041]) (MAD79) (S4). MovieeTicket Authenticating Device MAD79 (Paragraph [0041]) sends in awireless fashion a user data granted signal, which is received byCommunication Device 200 (S5). Here, the user data granted signal is thesignal which indicates that the user data (e.g., User Data#4) isauthenticated and thereby the user of Communication Device 200 isallowed to go through Admission Gate AG79 (Paragraph [0041]). CPU 211 ofCommunication Device 200 stores the user data granted signal in WorkArea 20679b4 (Paragraph [0034]) (S6), and displays the user data grantednotification data on LCD 201 (FIG. 1) (S7). Here, the user data grantednotification data is an image data designed to be displayed on LCD 201(FIG. 1) which indicates that the user data (e.g., User Data#4) isauthenticated and thereby the user of Communication Device 200 isallowed to go through Admission Gate AG79 (Paragraph [0041]). If themovie theater has no Admission Gate AG79 (Paragraph [0041]) or AdmissionGate AG79 (Paragraph [0041]) is not functioning, the attendant of themovie theater may visually confirm the user data granted notificationdisplayed on LCD 201 (FIG. 1), and thereby allow the user ofCommunication Device 200 to enter the movie theater.

Paragraph [0058]—This Paragraph [0058] illustrate(s) User Data DeletingSoftware H79c5a (Paragraph [0030]) of Host H (Paragraph [0022]) and UserData Deleting Software MAD79c5a (Paragraph [0046]) of Movie eTicketAuthenticating Device MAD79 (Paragraph [0041]), which delete the userdata stored in Movie eTicket Authenticating Device MAD79 (Paragraph[0041]). In the present embodiment, Movie eTicket Authenticating DeviceMAD79 (Paragraph [0041]) sends the user data expiration signal, which isreceived by Host H (S1). Here, the user data expiration signal is thesignal which indicates that the user of Communication Device 200 hasgone through Admission Gate AG79 (Paragraph [0041]) and, thereby, theuser data (e.g., User Data#4) is no longer valid. In response to theuser data expiration signal, Host H deletes the user ID (e.g., User#4)and the user data (e.g., User Data#4) stored in User Data Storage AreaH79b2 (Paragraph [0028]) (S2).

Paragraph [0059]—<<Movie eTicket Function—Another Embodiment02>>

Paragraph [0060]—Paragraph [0061] through Paragraph [0070] illustrate(s)another embodiment of the present function wherein the user data, aswell as the purchase data, is utilized for performing the admissionprocess.

Paragraph [0061]—This Paragraph [0061] illustrate(s) the softwareprograms stored in Movie eTicket Software Storage Area H79c (Paragraph[0025]). In the present embodiment, Movie eTicket Software Storage AreaH79c stores Movie Data Selecting Software H79c1, Purchase Data ProducingSoftware H79c2, Purchase Data/User Data Updating Software H79c3b, andPurchase Data/User Data Deleting Software H79c5b. Movie Data SelectingSoftware H79c1 is the software program described in Paragraph [0066].Purchase Data Producing Software H79c2 is the software program describedin Paragraph [0067]. Purchase Data/User Data Updating Software H79c3b isthe software program described in Paragraph [0068]. Purchase Data/UserData Deleting Software H79c5b is the software program described inParagraph [0069].

Paragraph [0062]—This Paragraph [0062] illustrate(s) the softwareprograms stored in Movie eTicket Software Storage Area 20679c (Paragraph[0033]). In the present embodiment, Movie eTicket Software Storage Area20679c stores Movie Data Selecting Software 20679c1, Purchase DataProducing Software 20679c2, and Purchase Data/User Data AuthenticatingSoftware 20679c4b. Movie Data Selecting Software 20679c1 is the softwareprogram described in Paragraph [0066]. Purchase Data Producing Software20679c2 is the software program described in Paragraph [0067]. PurchaseData/User Data Authenticating Software 20679c4b is the software programdescribed in Paragraph [0069].

Paragraph [0063]—This Paragraph [0063] illustrate(s) the data stored inUser Data Storage Area MAD79b2 (Paragraph [0043]). In the presentembodiment, User Data Storage Area MAD79b2 comprises two columns, i.e.,‘User ID’ and ‘User Data’. Column ‘User ID’ stores the user IDs, andeach user ID is an identification of the user data stored in column‘User Data’. Column ‘User Data’ stores the user data, and each user dataincludes name, home address, phone number, email address, and creditcard information. Here, the name represents the name of the user ofCommunication Device 200, the home address represents the home addressof the user, the phone number represents the phone number of the user,the email address represents the email address of the user, and thecredit card information represents the credit card information of theuser. In the present embodiment, User Data Storage Area MAD79b2 storesthe following data: the user ID ‘User#1’ and the user data ‘User Data#1(Name#1, Home Address#1, Phone Number#1, Email Address#1, Credit CardInformation#1)’; the user ID ‘User#2’ and the user data ‘User Data#2(Name#2, Home Address#2, Phone Number#2, Email Address#2, Credit CardInformation#2)’; the user ID ‘User#3’ and the user data ‘User Data#3(Name#3, Home Address#3, Phone Number#3, Email Address#3, Credit CardInformation#3)’; and the user ID ‘User#4’ and the user data ‘User Data#4(Name#4, Home Address#4, Phone Number#4, Email Address#4, Credit CardInformation#4)’.

Paragraph [0064]—This Paragraph [0064] illustrate(s) the data stored inPurchase Data Storage Area MAD79b1 (Paragraph [0043]). In the presentembodiment, Purchase Data Storage Area MAD79b1 comprises two columns,i.e., ‘User ID’ and ‘Purchase Data’. Column ‘User ID’ stores the userIDs described in Paragraph [0063]. Column ‘Purchase Data’ stores thepurchase data, and each purchase data is composed of alphanumeric datawhich do not represent or indicate the user data. A unique alphanumericdata may be assigned to each purchase data so that each purchase data isdistinguished from the other purchase data. In the present embodiment,Purchase Data Storage Area MAD79b1 stores the following data: the userID ‘User#1’ and the corresponding purchase data ‘Purchase Data#1’; theuser ID ‘User#2’ and the corresponding purchase data ‘Purchase Data#2’;the user ID ‘User#3’ and the corresponding purchase data ‘PurchaseData#3’; and the user ID ‘User#4’ and the corresponding purchase data‘Purchase Data#4’. As another embodiment, a common alphanumeric data maybe assigned to all purchase data (i.e., Purchase Data#1, PurchaseData#2, Purchase Data#3, and Purchase Data#4 are composed of the samealphanumeric data).

Paragraph [0065]—This Paragraph [0065] illustrate(s) the softwareprograms stored in Authenticated Movie eTicket Software Storage AreaMAD79c (Paragraph [0042]). In the present embodiment, AuthenticatedMovie eTicket Software Storage Area MAD79c stores Purchase Data/UserData Updating Software MAD79c3b, Purchase Data/User Data AuthenticatingSoftware MAD79c4b, and Purchase Data/User Data Deleting SoftwareMAD79c5b. Purchase Data/User Data Updating Software MAD79c3b is thesoftware program described in Paragraph [0068]. Purchase Data/User DataAuthenticating Software MAD79c4b is the software program described inParagraph [0069]. Purchase Data/User Data Deleting Software MAD79c5b isthe software program described in Paragraph [0070].

Paragraph [0066]—This Paragraph [0066] illustrate(s) Movie DataSelecting Software H79c1 (Paragraph [0030]) of Host H (Paragraph [0022])and Movie Data Selecting Software 20679c1 (Paragraph [0038]) ofCommunication Device 200, which select the movie for which the movieeticket is to be purchased. In the present embodiment, Host H retrievesall movie IDs and movie data from Movie Data Storage Area H79b1(Paragraph [0027]), and sends these data to Communication Device 200 ina wireless fashion (S1). Upon receiving the movie IDs and the movie datafrom Host H, CPU 211 (FIG. 1) of Communication Device 200 stores thesedata in Movie Data Storage Area 20679b1 (Paragraph [0035]) (S2). CPU 211retrieves the movie data from Movie Data Storage Area 20679b1 (Paragraph[0035]) and displays a movie list on LCD 201 (FIG. 1) (S3). The user ofCommunication Device 200 selects a movie data (e.g., Movie Data#1) byutilizing Input Device 210 (FIG. 1) or via voice recognition system(S4).

Paragraph [0067]—This Paragraph [0067] illustrate(s) Purchase DataProducing Software H79c2 (Paragraph [0030]) of Host H (Paragraph [0022])and Purchase Data Producing Software 20679c2 (Paragraph [0038]) ofCommunication Device 200, which produce a purchase data. In the presentembodiment, CPU 211 (FIG. 1) of Communication Device 200 retrieves itsuser data (e.g., User Data#4) from User Data Storage Area 20679b2(Paragraph [0036]) (S1), and sends in a wireless fashion thecorresponding movie ID (e.g., Movie#1) of the movie data selected in S4(e.g., Movie Data#1) and the user data (e.g., User Data#4), which arereceived by Host H (S2). Host H retrieves the credit card information(e.g., Credit Card Information#4) from the user data (e.g., UserData#4), and initiates the credit card authentication process which is aprocess to authenticate the credit card information (e.g., Credit CardInformation#4) (S3). If the credit card information is authenticated,Host H produces a new user ID (e.g., User#4) and stores the user data(e.g., User Data#4) at the user ID (e.g., User#4) in User Data StorageArea H79b2 (Paragraph [0028]) (S4). Host H produces a purchase data(e.g., Purchase Data#4) and stores the data at the user ID (e.g.,User#4) in Purchase Data Storage Area H79b3 (Paragraph [0029]) (S5).Host H sends the purchase data (e.g., Purchase Data#4) in a wirelessfashion, and Communication Device 200 receives the data (S6). CPU 211 ofCommunication Device 200 stores the purchase data (e.g., PurchaseData#4) in Purchase Data Storage Area 20679b3 (Paragraph [0037]) (S7).

Paragraph [0068]—This Paragraph [0068] illustrate(s) Purchase Data/UserData Updating Software H79c3b (Paragraph [0030]) of Host H (Paragraph[0022]) and Purchase Data/User Data Updating Software MAD79c3b(Paragraph [0046]) of Movie eTicket Authenticating Device MAD79(Paragraph [0041]), which update the purchase data and the user datastored in Movie eTicket Authenticating Device MAD79 (Paragraph [0041]).In the present embodiment, Host H retrieves all user IDs and purchasedata from Purchase Data Storage Area H79b3 (Paragraph [0029]) (S1). HostH retrieves all user IDs and user data from User Data Storage Area H79b2(Paragraph [0028]) (S2). Host H sends the data retrieved in S1 and S2,and Movie eTicket Authenticating Device MAD79 (Paragraph [0041])receives the data (S3). Movie eTicket Authenticating Device MAD79(Paragraph [0041]) stores the user IDs and the purchase data in PurchaseData Storage Area MAD79b1 (Paragraph [0064]) (S4). Movie eTicketAuthenticating Device MAD79 (Paragraph [0041]) stores the user IDs andthe user data in User Data Storage Area MAD79b2 (Paragraph [0063]) (S5).

Paragraph [0069]—This Paragraph [0069] illustrate(s) Purchase Data/UserData Authenticating Software MAD79c4b (Paragraph [0046]) of MovieeTicket Authenticating Device MAD79 (Paragraph [0041]) and PurchaseData/User Data Authenticating Software 20679c4b (Paragraph [0038]) ofCommunication Device 200, which authenticate the purchase data and theuser data stored in Movie eTicket Authenticating Device MAD79 (Paragraph[0041]). In the present embodiment, CPU 211 (FIG. 1) of CommunicationDevice 200 retrieves the purchase data (e.g., Purchase Data#4) fromPurchase Data Storage Area 20679b3 (Paragraph [0037]) (S1). CPU 211retrieves the user data (e.g., User Data#4) from User Data Storage Area20679b2 (Paragraph [0036]) (S2). CPU 211 retrieves the movie data fromMovie Data Storage Area 20679b1 (Paragraph [0035]) (S3). CPU 211 sendsin a wireless fashion the data retrieved in S1, S2 and S3, and MovieeTicket Authenticating Device MAD79 (Paragraph [0041]) receives the data(S4). Movie eTicket Authenticating Device MAD79 (Paragraph [0041])stores the purchase data (e.g., Purchase Data#4), the user data (e.g.,User Data#4), and the movie data (e.g., Movie Data#1) in Work AreaMAD79b3 (Paragraph [0043]) (S5). Movie eTicket Authenticating DeviceMAD79 (Paragraph [0041]) performs the authentication process, i.e.,scans Purchase Data Storage Area MAD79b1 (Paragraph [0064]) (S6), andalso scans User Data Storage Area MAD79b2 (Paragraph [0063]) (S7). MovieeTicket Authenticating Device MAD79 (Paragraph [0041]) sends theadmission signal to Admission Gate Controller AGC79 (Paragraph [0041])to open Admission Gate AG79 (Paragraph [0041]) (S8). Movie eTicketAuthenticating Device MAD79 (Paragraph [0041]) sends in a wirelessfashion the purchase data granted signal, which is received byCommunication Device 200 (S9). Here, the purchase data granted signal isthe signal which indicates that the purchase data (e.g., PurchaseData#4) is authenticated and thereby the user of Communication Device200 is allowed to go through Admission Gate AG79 (Paragraph [0041]). CPU211 (FIG. 1) of Communication Device 200 stores the purchase datagranted signal in Work Area 20679b4 (Paragraph [0034]) (S10). MovieeTicket Authenticating Device MAD79 (Paragraph [0041]) sends in awireless fashion the user data granted signal, which is received byCommunication Device 200 (S11). Here, the user data granted signal isthe signal which indicates that the user data (e.g., User Data#4) isauthenticated and thereby the user of Communication Device 200 isallowed to go through Admission Gate AG79 (Paragraph [0041]). CPU 211stores the user data granted signal in Work Area 20679b4 (Paragraph[0034]) (S12). CPU 211 displays the Movie eTicket granted notificationdata on LCD 201 (FIG. 1) (S13). Here, the movie eticket grantednotification data is an image data designed to be displayed on LCD 201(FIG. 1) which indicates that the user of Communication Device 200 isallowed to go through Admission Gate AG79 (Paragraph [0041]). If themovie theater has no Admission Gate AG79 (Paragraph [0041]) or AdmissionGate AG79 (Paragraph [0041]) is not functioning, the attendant of themovie theater may visually confirm the purchase data grantednotification displayed on LCD 201 (FIG. 1), and thereby allow the userof Communication Device 200 to enter the movie theater. The movieeticket granted notification data may include the user data of the userof Communication Device 200 and the movie data described hereinbefore.

Paragraph [0070]—This Paragraph [0070] illustrate(s) Purchase Data/UserData Deleting Software H79c5b (Paragraph [0030]) of Host H (Paragraph[0022]) and Purchase Data/User Data Deleting Software MAD79c5b(Paragraph [0046]) of Movie eTicket Authenticating Device MAD79(Paragraph [0041]), which delete the purchase data and the user datastored in Movie eTicket Authenticating Device MAD79 (Paragraph [0041]).In the present embodiment, Movie eTicket Authenticating Device MAD79(Paragraph [0041]) sends the Purchase Data/User Data expiration signal,which is received by Host H (S1). Here, the purchase data/user dataexpiration signal is the signal which indicates that the user ofCommunication Device 200 has gone through Admission Gate AG79 (Paragraph[0041]) and, thereby, the purchase data (e.g., Purchase Data#4) and theuser data (e.g., User Data#4) are no longer valid. Host H deletes thepurchase data (e.g., Purchase Data#4) and the user ID (e.g., User#4)stored in Purchase Data Storage Area H79b3 (Paragraph [0029]) (S2). HostH deletes the user ID (e.g., User#4) and the user data (e.g., UserData#4) stored in User Data Storage Area H79b2 (Paragraph [0028]) (S3).

Paragraph [0071]—The term ‘movie eticket’ utilized in this specificationmeans the purchase data granted signal (Paragraph [0048]), the purchasedata granted notification data (Paragraph [0048]), the user data grantedsignal (Paragraph [0057]), the user data granted notification data(Paragraph [0057]), and/or any data which represents that the user ofCommunication Device 200 has duly purchased the movie ticket and/or hasthe right to enter the movie theater to watch the certain movie (e.g.,Movie#1).

Paragraph [0072]—<<Carrier Prepaid eCard Function>>

Paragraph [0073]—Paragraph [0074] through Paragraph [0104] illustrate(s)the carrier prepaid ecard function which enables to purchase prepaidecards via Communication Device 200 and board carrier by utilizingCommunication Device 200 without utilizing paper tickets. Here, thecarrier prepaid ecard is a prepaid card stored in Communication Device200 in an electronic form (i.e., ecard). A certain amount of credit(e.g., the credit equivalent to $40) is stored in the carrier prepaidecard, and carrier fare is charged thereto every time the user ofCommunication Device 200 boards a carrier. The term ‘carrier’ includesany carrier or transportation system capable of carrying passengers,such as railway train, bus, taxi, airplane, etc.

Paragraph [0074]—This Paragraph [0074] illustrate(s) the storage areaincluded in Host H (Paragraph [0022]). In the present embodiment, Host Hincludes Carrier Prepaid eCard Information Storage Area H80a of whichthe data and the software programs stored therein are described inParagraph [0075].

Paragraph [0075]—This Paragraph [0075] illustrate(s) the storage areasincluded in Carrier Prepaid eCard Information Storage Area H80a(Paragraph [0074]). In the present embodiment, Carrier Prepaid eCardInformation Storage Area H80a includes Carrier Prepaid eCard DataStorage Area H80b and Carrier Prepaid eCard Software Storage Area H80c.Carrier Prepaid eCard Data Storage Area H80b stores the data necessaryto implement the present function on the side of Host H (Paragraph[0022]), such as the ones described in Paragraph through Paragraph[0080]. Carrier Prepaid eCard Software Storage Area H80c stores thesoftware programs necessary to implement the present function on theside of Host H, such as the ones described in Paragraph [0081].

Paragraph [0076]—This Paragraph [0076] illustrate(s) the storage areasincluded in Carrier Prepaid eCard Data Storage Area H80b (Paragraph[0075]). In the present embodiment, Carrier Prepaid eCard Data StorageArea H80b includes Prepaid eCard Type Data Storage Area H80b1, User DataStorage Area H80b2, Purchased eCard Type Data Storage Area H80b3,Balance Data Storage Area H80b4, and Work Area H80b5. Prepaid eCard TypeData Storage Area H80b1 stores the data described in Paragraph [0077].User Data Storage Area H80b2 stores the data described in Paragraph[0078]. Purchased eCard Type Data Storage Area H80b3 stores the datadescribed in Paragraph [0079]. Balance Data Storage Area H80b4 storesthe data described in Paragraph [0080]. Work Area H80b5 is utilized as awork area to perform calculation and temporarily store data.

Paragraph [0077]—This Paragraph [0077] illustrate(s) the data stored inPrepaid eCard. Type Data Storage Area H80b1 (Paragraph [0076]). In thepresent embodiment, Prepaid eCard Type Data Storage Area H80b1 comprisestwo columns, i.e., ‘Prepaid eCard Type ID’ and ‘Prepaid eCard TypeData’. Column ‘Prepaid eCard Type ID’ stores the prepaid ecard type IDs,and each prepaid ecard type ID is an identification of the correspondingprepaid ecard type data stored in column ‘Prepaid eCard Type Data’.Column ‘Prepaid eCard Type Data’ stores the prepaid ecard type data, andeach prepaid ecard type data represents the type of the prepaid ecardcapable to be purchased. In the present embodiment, Prepaid eCard TypeData Storage Area H80b1 stores the following data: the prepaid ecardtype ID ‘Prepaid eCard Type#1’ and the corresponding prepaid ecard typedata ‘Prepaid eCard Type Data#1’; the prepaid ecard type ID ‘PrepaideCard Type#2’ and the corresponding prepaid ecard type data ‘PrepaideCard Type Data#2’; the prepaid ecard type ID ‘Prepaid eCard Type#3’ andthe corresponding prepaid ecard type data ‘Prepaid eCard Type Data#3’;and the prepaid ecard type ID ‘Prepaid eCard Type#4’ and thecorresponding prepaid ecard type data ‘Prepaid eCard Type Data#4’. Here,the prepaid ecard type data ‘Prepaid eCard Type Data#1’ represents thecredit equivalent to the amount of $10; the prepaid ecard type data‘Prepaid eCard Type Data#2’ represents the credit equivalent to theamount of $20; the prepaid ecard type data ‘Prepaid eCard Type Data#3’represents the credit equivalent to the amount of $30; and the prepaidecard type data ‘Prepaid eCard Type Data#4’ represents the creditequivalent to the amount of $40.

Paragraph [0078]—This Paragraph [0078] illustrate(s) the data stored inUser Data Storage Area H80b2 (Paragraph [0076]). In the presentembodiment, User Data Storage Area H80b2 comprises two columns, i.e.,‘User ID’ and ‘User Data’. Column ‘User ID’ stores the user IDs, andeach user ID is an identification of the corresponding user data storedin column ‘User Data’. Column ‘User Data’ stores the user data, and eachuser data includes name, home address, phone number, email address, andcredit card information. Here, the name represents the name of the userof Communication Device 200, the home address represents the homeaddress of the user, the phone number represents the phone number of theuser, the email address represents the email address of the user, andthe credit card information represents the credit card information ofthe user. In the present embodiment, User Data Storage Area H80b2 storesthe following data: the user ID ‘User#1’ and the user data ‘User Data#1(Name#1, Home Address#1, Phone Number#1, Email Address#1, Credit CardInformation#1)’; the user ID ‘User#2’ and the user data ‘User Data#2(Name#2, Home Address#2, Phone Number#2, Email Address#2, Credit CardInformation#2)’; the user ID ‘User#3’ and the user data ‘User Data#3(Name#3, Home Address#3, Phone Number#3, Email Address#3, Credit CardInformation#3)’; and the user ID ‘User#4’ and the user data ‘User Data#4(Name#4, Home Address#4, Phone Number#4, Email Address#4, Credit CardInformation#4)’.

Paragraph [0079]—This Paragraph [0079] illustrate(s) the data stored inPurchased eCard Type Data Storage Area H80b3 (Paragraph [0076]). In thepresent embodiment, Purchased eCard Type Data Storage Area H80b3comprises two columns, i.e., ‘User ID’ and ‘Purchased eCard Type Data’.Column ‘User ID’ stores the user IDs described hereinbefore. Column‘Purchased eCard Type Data’ stores the purchased ecard type data, andeach purchased ecard type data represents the type of the carrier (e.g.,train) prepaid ecard purchased by the user of the corresponding user ID.In the present embodiment, Purchased eCard Type Data Storage Area H80b3stores the following data: the user ID ‘User#1’ and the correspondingpurchased ecard type data ‘Prepaid eCard Type Data#2’; the user ID‘User#2’ and the corresponding purchased ecard type data ‘Prepaid eCardType Data#2’; the user ID ‘User#3’ and the corresponding purchased ecardtype data ‘Prepaid eCard Type Data#4’; and the user ID ‘User#4’ and thecorresponding purchased ecard type data ‘Prepaid eCard Type Data#4’. Theforegoing data represents that the user whose user ID is ‘User#1’ haspurchased the carrier prepaid ecard of the credit equivalent to theamount of $20; the user whose user ID is ‘User#2’ has purchased thecarrier prepaid ecard of the credit equivalent to the amount of $20; theuser whose user ID is ‘User#3’ has purchased the carrier prepaid ecardof the credit equivalent to the amount of $40; and the user whose userID is ‘User#4’ has purchased the carrier prepaid ecard of the creditequivalent to the amount of $40.

Paragraph [0080]—This Paragraph [0080] illustrate(s) the data stored inBalance Data Storage Area H80b4 (Paragraph [0076]). In the presentembodiment, Balance Data Storage Area H80b4 comprises two columns, i.e.,‘User ID’ and ‘Balance Data’. Column ‘User ID’ stores the user IDsdescribed hereinbefore. Column ‘Balance Data’ stores the balance data,and each balance data represents the outstanding balance or theremaining credit of the carrier prepaid ecard. In the presentembodiment, Balance Data Storage Area H80b4 stores the following data:the user ID ‘User#1’ and the corresponding balance data ‘BalanceData#1’; the user ID ‘User#2’ and the corresponding balance data‘Balance Data#2’; the user ID ‘User#3’ and the corresponding balancedata ‘Balance Data#3’; and the user ID ‘User#4’ and the correspondingbalance data ‘Balance Data#4’. Here, the balance data ‘Balance Data#1’represents the credit equivalent to the amount of $20; the balance data‘Balance Data#2’ represents the credit equivalent to the amount of $20;the balance data ‘Balance Data#3’ represents the credit equivalent tothe amount of $40; and the balance data ‘Balance Data#4’ represents thecredit equivalent to the amount of $35. The foregoing balance dataindicates that the users whose user IDs are User#1 through #3 have notyet used the carrier prepaid ecard yet, whereas the user whose user IDis User#4 has used the carrier prepaid ecard for $5.

Paragraph [0081]—This Paragraph [0081] illustrate(s) the softwareprograms stored in Carrier Prepaid eCard Software Storage Area H80c(Paragraph [0075]). In the present embodiment, Carrier Prepaid eCardSoftware Storage Area H80c stores Carrier Prepaid eCard SelectingSoftware H80c1, Charging Device Updating Software H80c2, eCardAuthenticating Software H80c3, Balance Data Updating Software H80c5, andeCard Charged Notifying Software H80c6. Carrier Prepaid eCard SelectingSoftware H80c1 is the software program described in Paragraph [0091].Charging Device Updating Software H80c2 is the software programdescribed in Paragraph [0099]. eCard Authenticating Software H80c3 isthe software program described in Paragraph [0101]. Balance DataUpdating Software H80c5 is the software program described in Paragraph[0103]. eCard Charged Notifying Software H80c6 is the software programdescribed in Paragraph [0104].

Paragraph [0082]—This Paragraph [0082] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Communication Device 200 (e.g., DeviceA). In the present embodiment, RAM 206 includes Carrier Prepaid eCardInformation Storage Area 20680a of which the data and the softwareprograms stored therein are described in Paragraph [0083].

Paragraph [0083]—This Paragraph [0083] illustrate(s) the storage areasincluded in Carrier Prepaid eCard Information Storage Area 20680a(Paragraph [0082]). In the present embodiment, Carrier Prepaid eCardInformation Storage Area 20680a includes Carrier Prepaid eCard DataStorage Area 20680b and Carrier Prepaid eCard Software Storage Area20680c. Carrier Prepaid eCard Data Storage Area 20680b stores the datanecessary to implement the present function on the side of CommunicationDevice 200, such as the ones described in Paragraph [0085] throughParagraph [0089]. Carrier Prepaid eCard Software Storage Area 20680cstores the software programs necessary to implement the present functionon the side of Communication Device 200, such as the ones described inParagraph [0090].

Paragraph [0084]—The data and/or the software programs stored in CarrierPrepaid eCard Information Storage Area 20680a (Paragraph [0082]) may bedownloaded from Host H (Paragraph [0022]) in the manner described inParagraph [0416] through Paragraph [0422]. Paragraph [0085]—ThisParagraph [0085] illustrate(s) the storage areas included in CarrierPrepaid eCard Data Storage Area 20680b (Paragraph [0083]). In thepresent embodiment, Carrier Prepaid eCard Data Storage Area 20680bincludes Prepaid eCard Type Data Storage Area 20680b1, User Data StorageArea 20680b2, Purchased eCard Type Data Storage Area 20680b3, BalanceData Storage Area 20680b4, and Work Area 20680b5. Prepaid eCard TypeData Storage Area 20680b1 stores the data described in Paragraph [0086].User Data Storage Area 20680b2 stores the data described in Paragraph[0087]. Purchased eCard Type Data Storage Area 20680b3 stores the datadescribed in Paragraph [0088]. Balance Data Storage Area 20680b4 storesthe data described in Paragraph [0089]. Work Area 20680b5 is utilized asa work area to perform calculation and temporarily store data.

Paragraph [0086]—This Paragraph [0086] illustrate(s) the data stored inPrepaid eCard Type Data Storage Area 20680b1 (Paragraph [0085]). In thepresent embodiment, Prepaid eCard Type Data Storage Area 20680b1comprises two columns, i.e., ‘Prepaid eCard Type ID’ and ‘Prepaid eCardType Data’. Column ‘Prepaid eCard Type ID’ stores the prepaid ecard typeIDs, and each prepaid ecard type ID is an identification of thecorresponding prepaid ecard type data stored in column ‘Prepaid eCardType Data’. Column ‘Prepaid eCard Type Data’ stores the prepaid ecardtype data, and each prepaid ecard type data represents the type of theprepaid ecard capable to be purchased. In the present embodiment,Prepaid eCard Type Data Storage Area 20680b1 stores the following data:the prepaid ecard type ID ‘Prepaid eCard Type#1’ and the correspondingprepaid ecard type data ‘Prepaid eCard Type Data#1’; the prepaid ecardtype ID ‘Prepaid eCard Type#2’ and the corresponding prepaid ecard typedata ‘Prepaid eCard Type Data#2’; the prepaid ecard type ID ‘PrepaideCard Type#3’ and the corresponding prepaid ecard type data ‘PrepaideCard Type Data#3’; and the prepaid ecard type ID ‘Prepaid eCard Type#4’and the corresponding prepaid ecard type data ‘Prepaid eCard TypeData#4’. Here, the prepaid ecard type data ‘Prepaid eCard Type Data#1’represents the credit equivalent to the amount of $10; the prepaid ecardtype data ‘Prepaid eCard Type Data#2’ represents the credit equivalentto the amount of $20; the prepaid ecard type data ‘Prepaid eCard TypeData#3’ represents the credit equivalent to the amount of $30; and theprepaid ecard type data ‘Prepaid eCard Type Data#4’ represents thecredit equivalent to the amount of $40.

Paragraph [0087]—This Paragraph [0087] illustrate(s) the data stored inUser Data Storage Area 20680b2 (Paragraph [0085]). In the presentembodiment, User Data Storage Area 20680b2 comprises two columns, i.e.,‘User ID’ and ‘User Data’. Column ‘User ID’ stores the user ID which isan identification of the user data stored in column ‘User Data’. Column‘User Data’ stores the user data which includes name, home address,phone number, email address, and credit card information. Here, the namerepresents the name of the user of Communication Device 200 (e.g.,device A), the home address represents the home address of the user ofCommunication Device 200 (e.g., device A), the phone number representsthe phone number of the user of Communication Device 200 (e.g., deviceA), the email address represents the email address of the user ofCommunication Device 200 (e.g., device A), and the credit cardinformation represents the credit card information of the user ofCommunication Device 200 (e.g., device A). In the present embodiment,User Data Storage Area 20680b2 stores the following data: the user ID‘User#4’ and the user data ‘User Data#4 (Name#4, Home Address#4, PhoneNumber#4, Email Address#4, Credit Card Information#4)’.

Paragraph [0088]—This Paragraph [0088] illustrate(s) the data stored inPurchased eCard Type Data Storage Area 20680b3 (Paragraph [0085]). Inthe present embodiment, Purchased eCard Type Data Storage Area 20680b3comprises two columns, i.e., ‘User ID’ and ‘Purchased eCard Type Data’.Column ‘User ID’ stores the user ID described hereinbefore. Column‘Purchased eCard Type Data’ stores the purchased ecard type data whichrepresents the type of the carrier (e.g., train) prepaid ecard purchasedby the user of the corresponding user ID. In the present embodiment,Purchased eCard Type Data Storage Area 20680b3 stores the followingdata: the user ID ‘User#4’ of the user of Communication Device 200(e.g., Device A) and the corresponding purchased ecard type data‘Prepaid eCard Type Data#4’. The foregoing data represents that the userwhose user ID is ‘User#4’ has purchased the carrier prepaid ecard of thecredit equivalent to the amount of $40.

Paragraph [0089]—This Paragraph [0089] illustrate(s) the data stored inBalance Data Storage Area 20680b4 (Paragraph [0085]). In the presentembodiment, Balance Data Storage Area 20680b4 comprises two columns,i.e., ‘User ID’ and ‘Balance Data’. Column ‘User ID’ stores the user IDsdescribed hereinbefore. Column ‘Balance Data’ stores the balance datawhich represents the outstanding balance or the remaining credit of thecarrier prepaid ecard. In the present embodiment, Balance Data StorageArea 20680b4 stores the following data: the user ID ‘User#4’ of the userof Communication Device 200 (e.g., Device A) and the correspondingbalance data ‘Balance Data#4’. Here, the balance data ‘Balance Data#4’represents the credit equivalent to the amount of $35. The foregoingbalance data indicates that the user whose user ID is User#4 has usedthe carrier prepaid ecard for $5.

Paragraph [0090]—This Paragraph [0090] illustrate(s) the softwareprograms stored in Carrier Prepaid eCard Software Storage Area 20680c(Paragraph [0083]). In the present embodiment, Carrier Prepaid eCardSoftware Storage Area 20680c stores Carrier Prepaid eCard SelectingSoftware 20680c1, eCard Authenticating Software 20680c3, eCard ChargingSoftware 20680c4, and eCard Charged Notifying Software 20680e6. CarrierPrepaid eCard Selecting Software 20680c1 is the software programdescribed in Paragraph [0091]. eCard Authenticating Software 20680c3 isthe software program described in Paragraph [0101]. eCard ChargingSoftware 20680c4 is the software program described in Paragraph [0102].eCard Charged Notifying Software 20680c6 is the software programdescribed in Paragraph [0104]. Paragraph [0091]—This Paragraph [0091]illustrate(s) Carrier Prepaid eCard Selecting Software H80c1 (Paragraph[0081]) of Host H (Paragraph [0022]) and Carrier Prepaid eCard SelectingSoftware 20680c1 (Paragraph [0090]) of Communication Device 200, whichselect and purchase the carrier prepaid ecard. In the presentembodiment, Host H retrieves all prepaid ecard type IDs and prepaidecard type data from Prepaid eCard Type Data Storage Area H80b1(Paragraph [0077]) and sends the data to Communication Device 200 (S1).CPU 211 (FIG. 1) of Communication Device 200 receives the prepaid ecardtype ID and the prepaid ecard type data from Host H and stores the datain Prepaid eCard Type Data Storage Area 20680b1 (Paragraph [0086]) (S2).CPU 211 retrieves all prepaid ecard type data from Prepaid eCard TypeData Storage Area 20680b1 (Paragraph [0086]) and displays a list ofprepaid ecard type data on LCD 201 (FIG. 1) (S3). The user ofCommunication Device 200 (e.g., Device A) selects a prepaid ecard typedata (e.g., Prepaid eCard Type Data#4) (S4). CPU 211 stores the prepaidecard type data (e.g., Prepaid eCard Type Data#4) selected in previousstep in Purchased eCard Type Data Storage Area 20680b3 (Paragraph[0088]) (S5). CPU 211 retrieves the user ID (e.g., User#4) and the userdata (e.g., User Data#4) from User Data Storage Area 20680b2 (Paragraph[0087]) (S6). CPU 211 sends the prepaid ecard type ID (e.g., PrepaideCard Type#4) of the prepaid ecard type Data (e.g., Prepaid eCard TypeData#4) stored in S5, the user ID (e.g., User#4) and the user data(e.g., User Data#4), which are received by Host H (S7). Host H storesthe user ID (e.g., User#4) and the user data (e.g., User Data#4) in UserData Storage Area H80b2 (Paragraph [0078]) (S8). Host H stores the userID (e.g., User#4) and the prepaid ecard type ID (e.g., Prepaid eCardType#4) in Purchased eCard Type Data Storage Area H80b3 (Paragraph[0079]) (S9). Host H retrieves the credit card information (e.g., CreditCard Information#4) from User Data Storage Area H80b2 and chargesthereto for the carrier prepaid ecard (e.g., $40) (S10).

Paragraph [0092]—This Paragraph [0092] illustrate(s) the function ofCarrier Prepaid eCard Charging Device TPCC80, Admission Gate ControllerAGC80, and Admission Gate AG80. In the present embodiment, CarrierPrepaid eCard Charging Device TPCC80 is connected to Admission GateController AGC80, and Admission Gate Controller AGC80 is connected toAdmission Gate AG80. Admission Gate AG80 is the gate installed near orat the boarding entrance of a carrier. Admission Gate AG80 is normallyclosed, and opens only when an admission gate signal is sent fromAdmission Gate Controller AGC80. Passengers are able to go throughAdmission Gate AG80 when it is open. Admission Gate Controller AGC80 isa device to control Admission Gate AG80. Admission Gate Controller AGC80sends the admission gate signal which is a command to open the gate ofAdmission Gate AG80. The admission gate signal is sent when AdmissionGate Controller AGC80 receives an admission signal sent from CarrierPrepaid eCard Charging Device TPCC80. Here, the admission signal is asignal which indicates that a carrier prepaid ecard is authenticated ofwhich the process therefor is explained hereinafter. The location ofAdmission Gate AG80 may differ depending on the type of the carrier. Forexample, Admission Gate AG80 may be installed in a railway station ifthe carrier is a railway train. Admission Gate AG80 may be installed inthe carrier if the carrier is a bus. Admission Gate AG80 may beinstalled in the carrier if the carrier is a taxi. Admission Gate AG80may be installed in an airport if the carrier is an airplane.

Paragraph [0093]—This Paragraph [0093] illustrate(s) the storage areasincluded in Carrier Prepaid eCard Charging Information Storage AreaTPCC80a (Paragraph [0092]). In the present embodiment, Carrier PrepaideCard Charging Information Storage Area TPCC80a includes Carrier PrepaideCard Charging Data Storage Area TPCC80b and Carrier Prepaid eCardAuthenticating Software Storage Area TPCC80c. Carrier Prepaid eCardCharging Data Storage Area TPCC80b stores the data necessary toimplement the present function on the side of Carrier Prepaid eCardCharging Device TPCC80 (Paragraph [0092]), such as the ones described inParagraph [0094] through Paragraph [0097]. Carrier Prepaid eCardAuthenticating Software Storage Area TPCC80c stores the softwareprograms necessary to implement the present function on the side ofCarrier Prepaid eCard Charging Device TPCC80, such as the ones describedin Paragraph [0098].

Paragraph [0094]—This Paragraph [0094] illustrate(s) the storage areasincluded in Carrier Prepaid eCard Charging Data Storage Area TPCC80b(Paragraph [0093]). In the present embodiment, Carrier Prepaid eCardCharging Data Storage Area TPCC80b includes User Data Storage AreaTPCC80b2, Purchased eCard Type Data Storage Area TPCC80b3, Balance DataStorage Area TPCC80b4, and Work Area TPCC80b5. User Data Storage AreaTPCC80b2 stores the data described in Paragraph [0095]. Purchased eCardType Data Storage Area TPCC80b3 stores the data described in Paragraph[0096]. Balance Data Storage Area TPCC80b4 stores the data described inParagraph [0097]. Work Area TPCC80b5 is utilized as a work area toperform calculation and temporarily store data.

Paragraph [0095]—This Paragraph [0095] illustrate(s) the data stored inUser Data Storage Area TPCC80b2 (Paragraph [0094]). In the presentembodiment, User Data Storage Area TPCC80b2 comprises two columns, i.e.,‘User ID’ and User Data'. Column ‘User ID’ stores the user IDs, and eachuser ID is an identification of the corresponding user data stored incolumn ‘User Data’. Column ‘User Data’ stores the user data, and eachuser data includes name, home address, phone number, email address, andcredit card information. Here, the name represents the name of the userof Communication Device 200, the home address represents the homeaddress of the user, the phone number represents the phone number of theuser, the email address represents the email address of the user, andthe credit card information represents the credit card information ofthe user. In the present embodiment, User Data Storage Area TPCC80b2stores the following data: the user ID ‘User#1’ and the user data ‘UserData#1 (Name#1, Home Address#1, Phone Number#1, Email Address#1, CreditCard Information#1)’; the user ID ‘User#2’ and the user data ‘UserData#2 (Name#2, Home Address#2, Phone Number#2, Email Address#2, CreditCard Information#2)’; the user ID ‘User#3’ and the user data ‘UserData#3 (Name#3, Home Address#3, Phone Number#3, Email Address#3, CreditCard Information#3)’; and the user ID ‘User#4’ and the user data ‘UserData#4 (Name#4, Home Address#4, Phone Number#4, Email Address#4, CreditCard Information#4)’.

Paragraph [0096]—This Paragraph [0096] illustrate(s) the data stored inPurchased eCard Type Data Storage Area TPCC80b3 (Paragraph [0094]). Inthe present embodiment, Purchased eCard Type Data Storage Area TPCC80b3comprises two columns, i.e., ‘User ID’ and ‘Purchased eCard Type Data’.Column ‘User ID’ stores the user IDs described hereinbefore. Column‘Purchased eCard Type Data’ stores the purchased ecard type data, andeach purchased ecard type data represents the type of the carrier (e.g.,train) prepaid ecard purchased by the user of the corresponding user ID.In the present embodiment, Purchased eCard Type Data Storage AreaTPCC80b3 stores the following data: the user ID ‘User#1’ and thecorresponding purchased ecard type data ‘Prepaid eCard Type Data#2’; theuser ID ‘User#2’ and the corresponding purchased ecard type data‘Prepaid eCard Type Data#2’; the user ID ‘User#3’ and the correspondingpurchased ecard type data ‘Prepaid eCard Type Data#4’; and the user ID‘User#4’ and the corresponding purchased ecard type data ‘Prepaid eCardType Data#4’. The foregoing data represents that the user whose user IDis ‘User#1’ has purchased the carrier prepaid ecard of the creditequivalent to the amount of $20; the user whose user ID is ‘User#2’ haspurchased the carrier prepaid ecard of the credit equivalent to theamount of $20; the user whose user ID is ‘User#3’ has purchased thecarrier prepaid ecard of the credit equivalent to the amount of $40; andthe user whose user ID is ‘User#4’ has purchased the carrier prepaidecard of the credit equivalent to the amount of $40.

Paragraph [0097]—This Paragraph [0097] illustrate(s) the data stored inBalance Data Storage Area TPCC80b4 (Paragraph [0094]). In the presentembodiment, Balance Data Storage Area TPCC80b4 comprises two columns,i.e., ‘User ID’ and ‘Balance Data’. Column ‘User ID’ stores the user IDsdescribed hereinbefore. Column ‘Balance Data’ stores the balance data,and each balance data represents the outstanding balance or theremaining credit of the carrier prepaid ecard. In the presentembodiment, Balance Data Storage Area TPCC80b4 stores the followingdata: the user ID ‘User#1’ and the corresponding balance data ‘BalanceData#1’; the user ID ‘User#2’ and the corresponding balance data‘Balance Data#2’; the user ID ‘User#3’ and the corresponding balancedata ‘Balance Data#3’; and the user ID ‘User#4’ and the correspondingbalance data ‘Balance Data#4’. Here, the balance data ‘Balance Data#1’represents the credit equivalent to the amount of $20; the balance data‘Balance Data#2’ represents the credit equivalent to the amount of $20;the balance data ‘Balance Data#3’ represents the credit equivalent tothe amount of $40; and the balance data ‘Balance Data#4’ represents thecredit equivalent to the amount of $35. The foregoing balance dataindicates that the users whose user IDs are User#1 through #3 have notyet used the carrier prepaid ecard yet, whereas the user whose user IDis User#4 has used the carrier prepaid ecard for $5.

Paragraph [0098]—This Paragraph [0098] illustrate(s) the softwareprograms stored in Carrier Prepaid eCard Authenticating Software StorageArea TPCC80c (Paragraph [0093]). In the present embodiment, CarrierPrepaid eCard Authenticating Software Storage Area TPCC80c storesCharging Device Updating Software TPCC80c2, eCard AuthenticatingSoftware TPCC80c3, eCard Charging Software TPCC80c4, and Balance DataUpdating Software TPCC80c5. Charging Device Updating Software TPCC80c2is the software program described in Paragraph [0099]. eCardAuthenticating Software TPCC80c3 is the software program described inParagraph [0101]. eCard Charging Software TPCC80c4 is the softwareprogram described in Paragraph [0102]. Balance Data Updating SoftwareTPCC80c5 is the software program described in Paragraph [0103].

Paragraph [0099]—This Paragraph [0099] illustrate(s) Charging DeviceUpdating Software H80c2 (Paragraph [0081]) of Host H (Paragraph [0022])and Charging Device Updating Software TPCC80c2 (Paragraph [0098]) ofCarrier Prepaid eCard Charging Device TPCC80 (Paragraph [0092]), whichupdate all data stored in Carrier Prepaid eCard Charging Data StorageArea TPCC80b (Paragraph [0094]). In the present embodiment, Host Hretrieves all data stored in User Data Storage Area H80b2 (Paragraph[0078]), Purchased eCard Type Data Storage Area H80b3 (Paragraph[0079]), and Balance Data Storage Area H80b4 (Paragraph [0080]) andsends the data to Carrier Prepaid eCard Charging Device TPCC80 (S1).Carrier Prepaid eCard Charging Device TPCC80 receives the data selectedin S1 from Host H (S2). Carrier Prepaid eCard Charging Device TPCC80stores the User IDs and the user data in User Data Storage Area TPCC80b2(Paragraph [0095]) (S3). Carrier Prepaid eCard Charging Device TPCC80stores the User IDs and the Purchased eCard Type Data in Purchased eCardType Data Storage Area TPCC80b3 (Paragraph [0096]) (S4). Carrier PrepaideCard Charging Device TPCC80 stores the User IDs and the balance data inBalance Data Storage Area H80b4 (Paragraph [0080]) (S5). The foregoingsequence is performed periodically, for example every morning at thepredetermined time.

Paragraph [0100]—This Paragraph [0100] illustrate(s) eCardAuthenticating Software TPCC80c3 (Paragraph [0098]) of Carrier PrepaideCard Charging Device TPCC80 (Paragraph [0092]) and eCard AuthenticatingSoftware 20680c3 (Paragraph [0090]) of Communication Device 200, whichauthenticate Communication Device 200 before allowing the user to gothrough Admission Gate AG80. In the present embodiment, CPU 211 (FIG. 1)of Communication Device 200 retrieves the user data (e.g., User Data#4)from User Data Storage Area 20680b2 (Paragraph [0087]) and sends thedata to Carrier Prepaid eCard Charging Device TPCC80 for authenticationpurposes (S1). Carrier Prepaid eCard Charging Device TPCC80 receives theuser data (e.g., User Data#4) and stores the data in Work Area TPCC80b5(Paragraph [0094]) (S2). Carrier Prepaid eCard Charging Device TPCC80(Paragraph [0092]) performs the user data authentication process (i.e.,scans User Data Storage Area TPCC80b2 (Paragraph [0095]) for matchinguser data) (TPCC80) (S3).

Paragraph [0101]—This Paragraph [0101] illustrate(s) eCardAuthenticating Software H80c3 (Paragraph [0081]) of Host H (Paragraph[0022]) and eCard Authenticating Software TPCC80c3 (Paragraph [0098]) ofCarrier Prepaid eCard Charging Device TPCC80 (Paragraph [0092]), whichauthenticate Communication Device 200 before allowing the user to gothrough Admission Gate AG80. The present embodiment illustrate(s)another embodiment of the sequence described in Paragraph [0100],wherein the user data authentication process is performed by Host Hinstead. In the present embodiment, CPU 211 (FIG. 1) of CommunicationDevice 200 retrieves the user data (e.g., User Data#4) from User DataStorage Area 20680b2 (Paragraph [0087]) and sends the data to CarrierPrepaid eCard Charging Device TPCC80 for authentication purposes (S1).Carrier Prepaid eCard Charging Device TPCC80 receives the user data(e.g., User Data#4) and stores the data in Work Area TPCC80b5 (Paragraph[0094]) (S2). Carrier Prepaid eCard Charging Device TPCC80 retrieves theuser data (e.g., User Data#4) from Work Area TPCC80b5 (Paragraph [0094])and sends the data to Host H (S3). Upon receiving the user data (e.g.,User Data#4), Host H performs the user data authentication process(i.e., scans User Data Storage Area H80b2 (Paragraph [0078]) formatching user data) (S4). If the matching user data (e.g., User Data#4)is found, Host H sends the user data authenticated signal, which isreceived by Carrier Prepaid eCard Charging Device TPCC80 (Paragraph[0092]) (S5). Here, the user data authenticated signal is a signalindicating that the user data (e.g., User Data#4) sent from CarrierPrepaid eCard Charging Device TPCC80 is authenticated and thereby theuser thereof is allowed to go through Admission Gate AG80.

Paragraph [0102]—This Paragraph [0102] illustrate(s) eCard ChargingSoftware TPCC80c4 (Paragraph [0098]) of Carrier Prepaid eCard ChargingDevice TPCC80 (Paragraph [0092]) and eCard Charging Software 20680c4(Paragraph [0090]) of Communication Device 200, which charge the carrierprepaid ecard. In the present embodiment, Carrier Prepaid eCard ChargingDevice TPCC80 (Paragraph [0092]) sends the ecard charge data in awireless fashion, which is received by Communication Device 200 (S1).Here, the ecard charge data is the data representing the carrier ticketfare charged (e.g., $5) to the carrier prepaid ecard stored inCommunication Device 200 to purchase the carrier ticket. eCard ChargeData also includes the name of the carrier station where the carrierprepaid ecard is charged and the date charged. CPU 211 (FIG. 1) ofCommunication Device 200 deducts the ecard charge data (e.g., $5) fromBalance Data#4 (e.g., $40) stored in Balance Data Storage Area 20680b4(Paragraph [0089]) and updates Balance Data#4 (e.g., $35) (S2). CarrierPrepaid eCard Charging Device TPCC80 deducts the ecard charge data(e.g., $5) from Balance Data#4 (e.g., $40) stored in Balance DataStorage Area TPCC80b4 (Paragraph [0097]) and updates Balance Data#4(e.g., $35) (S3). CPU 211 displays the data included in ecard chargedata (for example, the amount charged (e.g., $5), the name of thecarrier station where charged, and the date charged) on LCD 201 (FIG. 1)(S4). Carrier Prepaid eCard Charging Device TPCC80 sends the admissionsignal to Admission Gate Controller AGC80, and Admission Gate AG80(Paragraph [0092]) is open (S5). Here, admission signal is a signalwhich instructs Admission Gate AG80 to open its gate.

Paragraph [0103]—This Paragraph [0103] illustrate(s) Balance DataUpdating Software H80c5 (Paragraph [0081]) of Host H (Paragraph [0022])and Balance Data Updating Software TPCC80c5 (Paragraph [0098]) ofCarrier Prepaid eCard Charging Device TPCC80 (Paragraph [0092]), whichupdate the balance data stored in Balance Data Storage Area H80b4(Paragraph [0080]) of Host H. In the present embodiment, Carrier PrepaideCard Charging Device TPCC80 retrieves all user IDs and balance datafrom Balance Data Storage Area TPCC80b4 (Paragraph [0097]) and sends thedata to Host H (S1). Host H receives the data retrieved in S1 andupdates the balance data stored in Balance Data Storage Area H80b4(Paragraph [0080]), if any (S2). Paragraph [0104]—This Paragraph [0104]illustrate(s) eCard Charged Notifying Software H80c6 (Paragraph [0081])of Host H (Paragraph [0022]) and eCard Charged Notifying Software20680c6 (Paragraph [0090]) of Communication Device 200, which send anemail to the user of Communication Device 200 notifying that his/hercarrier prepaid ecard has been charged. In the present embodiment, HostH scans Balance Data Storage Area H80b4 (Paragraph [0080]) for anyupdated balance data (S1). Host H identifies the updated balance data(e.g., Balance Data#4) (S2). Host H identifies the corresponding user ID(e.g., User#4) in User Data Storage Area H80b2 (Paragraph [0078]) andretrieves the corresponding email address (e.g., Email Address#4) (S3).Host H sends the carrier prepaid ecard charged data to the email address(e.g., Email Address#4) stating the amount charged to the carrierprepaid ecard and the date charged, which is received by CommunicationDevice 200 (S4).

Paragraph [0105]—<<Communication Device 200 Installed In Carrier>>

Paragraph [0106]—This Paragraph [0106] illustrate(s) CommunicationDevice 200 which is installed in a carrier. In the present embodiment,Communication Device 200 can be installed in Carrier C82. Here, CarrierC82 is a carrier or transportation system designed to carrypassenger(s), such as automobile, motorcycle, railway train, taxi, bus,airplane, space ship, and space station. Communication Device 200 is thedevice described in FIG. 1.

Paragraph [0107]—<<In-Carrier Notifying Function>>

Paragraph [0108]—Paragraph [0109] through Paragraph [0127] illustrate(s)the in-carrier notifying function wherein a predetermined noticeindicating that the user of Communication Device 200 is currently incarrier is announced while the user is utilizing the voice communicationmode of Communication Device 200. The present function is useful whenthe user receives a phone call, however, needs to suggest the callerthat the user is required to hang up since he/she is currently riding acarrier. Here, the carrier may be any carrier or transportation systemdesigned to carry passenger(s), such as automobile, motorcycle, railwaytrain, taxi, bus, space ship, and space station.

Paragraph [0109]—This Paragraph [0109] illustrate(s) the antennasinstalled in Carrier CR83. Here, Carrier CR83 may be any carrier ortransportation system designed to carry passenger(s), such asautomobile, motorcycle, railway train, taxi, bus, space ship, and spacestation. In the present embodiment, six antennas, i.e., Antenna Ant83a,Antenna Ant83b, Antenna Ant83c, Antenna Ant83d, Antenna Ant83c, andAntenna Ant83f are installed in Carrier CR83. These antennas send andreceive data in a wireless fashion.

Paragraph [0110]—This Paragraph [0110] illustrate(s) the storage areaincluded in Carrier CR83 (Paragraph [0109]). In the present embodiment,Carrier CR83 includes In-Carrier Notifying Information Storage AreaCR83a of which the data and the software programs stored therein aredescribed in Paragraph [0111].

Paragraph [0111]—This Paragraph [0111] illustrate(s) the storage areasincluded in In-Carrier Notifying Information Storage Area CR83a(Paragraph [0110]). In the present embodiment, In-Carrier NotifyingInformation Storage Area CR83a includes In-Carrier Notifying DataStorage Area CR83b and In-Carrier Notifying Software Storage Area CR83c.In-Carrier Notifying Data Storage Area CR83b stores the data necessaryto implement the present function on the side of Carrier CR83 (Paragraph[0109]), such as the ones described in Paragraph and Paragraph [0113].In-Carrier Notifying Software Storage Area CR83c stores the softwareprograms necessary to implement the present function on the side ofCarrier CR83 (Paragraph [0109]), such as the one described in Paragraph[0114]. Paragraph [0112]—This Paragraph [0112] illustrate(s) the storageareas included in In-Carrier Notifying Data Storage Area CR83b(Paragraph [0111]). In the present embodiment, In-Carrier Notifying DataStorage Area CR83b includes In-Carrier Notifying Data Storage AreaCR83b1 and Work Area CR83b2. In-Carrier Notifying Data Storage AreaCR83b1 stores the data described in Paragraph [0113]. Work Area CR83b2is utilized as a work area to perform calculation and temporarily storedata.

Paragraph [0113]—This Paragraph [0113] illustrate(s) the data stored inIn-Carrier Notifying Data Storage Area CR83b1 (Paragraph [0112]). In thepresent embodiment, In-Carrier Notifying Data Storage Area CR83b1 storesthe in-carrier notifying data. Here, the in-carrier notifying data isthe data designed to be output from Antenna Ant83a (Paragraph [0109]),Antenna Ant83b (Paragraph [0109]), Antenna Ant83c (Paragraph [0109]),Antenna Ant83d (Paragraph [0109]), Antenna Ant83e (Paragraph [0109]),and Antenna Ant83f (Paragraph [0109]) in a wireless fashionrespectively, which induces Communication Device 200 to output themessage data described hereinafter.

Paragraph [0114]—This Paragraph [0114] illustrate(s) the softwareprograms stored in In-Carrier Notifying Software Storage Area CR83c(Paragraph [0111]). In the present embodiment, In-Carrier NotifyingSoftware Storage Area CR83c stores In-Carrier Notifying DataTransmitting Software CR83c1. In-Carrier Notifying Data TransmittingSoftware CR83c1 is the software program described in Paragraph [0115].

Paragraph [0115]—This Paragraph [0115] illustrate(s) In-CarrierNotifying Data Transmitting Software CR83 (Paragraph [0114]) of CarrierCR83 (Paragraph [0109]), which transmits the in-carrier notifying dataperiodically in a wireless fashion. In the present embodiment, CarrierCR83 (Paragraph [0109]) retrieves the in-carrier notifying data fromIn-Carrier Notifying Data Storage Area CR83b1 (Paragraph [0113]) (S1).Carrier CR83 (Paragraph [0109]) transmits the in-carrier notifying datafrom Antenna Ant83a (Paragraph [0109]), Antenna Ant83b (Paragraph[0109]), Antenna Ant83c (Paragraph [0109]), Antenna Ant83d (Paragraph[0109]), Antenna Ant83e (Paragraph [0109]), and Antenna Ant83f(Paragraph [0109]), respectively (S2). The foregoing sequence isperformed periodically.

Paragraph [0116]—This Paragraph [0116] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Communication Device 200. In the presentembodiment, RAM 206 includes In-Carrier Notifying Information StorageArea 20683a of which the data and the software programs stored thereinare described in Paragraph [0118].

Paragraph [0117]—The data and/or the software programs stored inIn-Carrier Notifying Information Storage Area 20683a (Paragraph [0116])may be downloaded from Host H (Paragraph [0022]) in the manner describedin Paragraph [0416] through Paragraph [0422].

Paragraph [0118]—This Paragraph [0118] illustrate(s) the storage areasincluded in In-Carrier Notifying Information Storage Area 20683a(Paragraph [0116]). In the present embodiment, In-Carrier NotifyingInformation Storage Area 20683a includes In-Carrier Notifying DataStorage Area 20683b and In-Carrier Notifying Software Storage Area20683c. In-Carrier Notifying Data Storage Area 20683b stores the datanecessary to implement the present function on the side of CommunicationDevice 200, such as the ones described in Paragraph [0119] throughParagraph [0122]. In-Carrier Notifying Software Storage Area 20683cstores the software programs necessary to implement the present functionon the side of Communication Device 200, such as the ones described inParagraph [0123].

Paragraph [0119]—This Paragraph [0119] illustrate(s) the storage areasincluded in In-Carrier Notifying Data Storage Area 20683b (Paragraph[0118]). In the present embodiment, In-Carrier Notifying Data StorageArea 20683b includes Message Data Storage Area 20683b1, Selected MessageID Storage Area 20683b2, User's Name Data Storage Area 20683b3, and WorkArea 20683b4. Message Data Storage Area 20683b1 stores the datadescribed in Paragraph [0120]. Selected Message ID Storage Area 20683b2stores the data described in Paragraph [0121]. User's Name Data StorageArea 20683b3 stores the data described in Paragraph [0122]. Work Area20683b4 is utilized as a work area to perform calculation andtemporarily store data.

Paragraph [0120]—This Paragraph [0120] illustrate(s) the data stored inMessage Data Storage Area 20683b1 (Paragraph [0119]). In the presentembodiment, Message Data Storage Area 20683b1 comprises two columns,i.e., ‘Message ID’ and ‘Message Data’. Column ‘Message ID’ stores themessage IDs, and each message ID is the identification of thecorresponding message data stored in column ‘Message Data’. Column‘Message Data’ stores the message data, and each message data is anaudio data indicating the following sentence in different expressions:‘The user is currently in carrier.’ In the present embodiment, MessageData Storage Area 20683b1 stores the following data: the message ID‘Message#1’ and the corresponding message data ‘Message Data#1’; themessage ID ‘Message#2’ and the corresponding message data ‘MessageData#2’; the message ID ‘Message#3’ and the corresponding message data‘Message Data#3’; and the message ID ‘Message#4’ and the correspondingmessage data ‘Message Data#4’. Here, Message Data#1 is the audio datastating the following message in male voice: ‘The user is currently incarrier.’ Message Data#2 is the audio data stating the following messagein female voice: ‘The user is currently in carrier.’ Message Data#3 isthe audio data stating the following message in male voice: ‘Pleasekindly understand that the user is not allowed to talk on the phone incarrier.’ Message Data#4 is the audio data stating the following messagein female voice: ‘Please kindly understand that the user is not allowedto talk on the phone in carrier.’

Paragraph [0121]—This Paragraph [0121] illustrate(s) the data stored inSelected Message ID Storage Area 20683b2 (Paragraph [0119]). SelectedMessage ID Storage Area 20683b2 stores one of the message IDs stored inMessage Data Storage Area 20683b1 (Paragraph [0120]). In the presentexample, Selected Message ID Storage Area 20683b2 stores the message ID‘Message#1’.

Paragraph [0122]—This Paragraph [0122] illustrate(s) the data stored inUser's Name Data Storage Area 20683b3 (Paragraph [0119]). User's NameData Storage Area 20683b3 stores the user's name data. Here, the user'sname data is an audio data representing the name of the user ofCommunication Device 200.

Paragraph [0123]—This Paragraph [0123] illustrate(s) the softwareprograms stored in In-Carrier Notifying Software Storage Area 20683c(Paragraph [0118]). In the present embodiment, In-Carrier NotifyingSoftware Storage Area 20683c stores In-Carrier Notifying Data DetectingSoftware 20683c2, Message Data Outputting Software 20683c3, and MessageData Selecting Software 20683c4. In-Carrier Notifying Data DetectingSoftware 20683c2 is the software program described in Paragraph [0124].Message Data Outputting Software 20683c3 is the software programdescribed in Paragraph [0125]. Message Data Selecting Software 20683c4is the software program described in Paragraph [0127].

Paragraph [0124]—This Paragraph [0124] illustrate(s) In-CarrierNotifying Data Detecting Software 20683c2 (Paragraph [0123]) ofCommunication Device 200, which detects the in-carrier notifying datatransmitted from Antenna Ant83a, Antenna Ant83b, Antenna Ant83c, AntennaAnt83d, Antenna Ant83e, and/or Antenna Ant83f. In the presentembodiment, CPU 211 (FIG. 1) of Communication Device 200 periodicallychecks the incoming data received from Antenna 218 (FIG. 1) (S1). If theincoming data is the in-carrier notifying data (S2), CPU 211 executesMessage Data Outputting Software 20683c3 (Paragraph [0125]) (S3).

Paragraph [0125]—This Paragraph [0125] illustrate(s) Message DataOutputting Software 20683c3 (Paragraph [0123]) of Communication Device200, which outputs the selected message data. In the present embodiment,CPU 211 (FIG. 1) of Communication Device 200 periodically checks thevoice communication mode status (S1). If Communication Device 200 is inthe voice communication mode (S2), CPU 211 identifies the message ID(e.g., Message#1) stored in Selected Message ID Storage Area 20683b2(Paragraph [0121]) (S3). CPU 211 retrieves the corresponding messagedata (e.g., Message Data#1) from Message Data Storage Area 20683b1(Paragraph [0120]) (S4), and outputs the message data (e.g., MessageData#1) from Speaker 216 (FIG. 1) (S5). In addition, CPU 211 merges themessage data (e.g., Message Data#1) with the outgoing user's voice dataand sends the data to the counter party whom user is conversing with(S6). As a result, the counter party hears the message data (e.g.,Message Data#1) from the speaker of his/her device (e.g., cellularphone).

Paragraph [0126]—This Paragraph [0126] illustrate(s) Message DataOutputting Software 20683c3 (Paragraph [0123]) of Communication Device200, which outputs the selected message data. The present embodimentillustrate(s) another embodiment of the sequence described in Paragraph[0125]. In the present embodiment, CPU 211 (FIG. 1) of CommunicationDevice 200 periodically checks the voice communication mode status (S1).If Communication Device 200 is in the voice communication mode (S2), CPU211 identifies the message ID (e.g., Message#1) stored In SelectedMessage ID Storage Area 20683b2 (Paragraph [0121]) (S3). CPU 211retrieves the corresponding message data (e.g., Message Data#1) fromMessage Data Storage Area 20683b1 (Paragraph [0120]) (S4). CPU 211retrieves the user's name data from User's Name Data Storage Area20683b3 (Paragraph [0122]) (S5). CPU 211 embeds the user's name data tothe message data (e.g., Message Data#1) and outputs the message data(e.g., Message Data#1) with user's name embedded from Speaker 216(FIG. 1) (S6). CPU 211 merges the message data (e.g., Message Data#1)with the user's name embedded to outgoing user's voice data and sendsthe data to counter party whom user is conversing with (S7). As aresult, the counter party hears the message data (e.g., Message Data#1)with the user's name embedded from the speaker of his/her device (e.g.,cellular phone). Assuming that the user's name is ‘Mr. John Doe’. Thefollowing is the message data (e.g., Message Data#1) without the user'sname embedded: ‘The user is currently in carrier.’ The following is themessage data (e.g., Message Data#1) with the user's name embedded: ‘Mr.John Doe is currently in carrier.’

Paragraph [0127]—This Paragraph [0127] illustrate(s) Message DataSelecting Software 20683c4 (Paragraph [0123]) of Communication Device200, which selects the message data which is output when Message DataOutputting Software 20683c3 (Paragraph [0125]) is executed. In thepresent embodiment, CPU 211 (FIG. 1) of Communication Device 200retrieves all message IDs from Message Data Storage Area 20683b1(Paragraph [0120]) and displays a list of the message IDs on LCD 201(FIG. 1) (S1). The user of Communication Device 200 selects a message ID(e.g., Message#1) by utilizing Input Device 210 (FIG. 1) or via voicerecognition system (S2). CPU 211 stores the message ID (e.g., Message#1)selected in the previous step in Selected Message ID Storage Area20683b2 (Paragraph [0121]) (S3).

Paragraph [0128]—<<Station Name Notifying Function>>

Paragraph [0129]—Paragraph [0130] through Paragraph [0147] illustrate(s)the station name notifying function which outputs the name of the nextstation at which the carrier is about to arrive. Here, the carrier maybe any carrier or transportation system designed to carry passenger(s),such as automobile, motorcycle, railway train, taxi, bus, space ship, orspace station. Here, the station is a location where the carrier picksup and/or drops off passenger(s). The station may be a railway station(if the carrier is a train), a bus stop (if the carrier is a bus), anairport (if the carrier is an airplane).

Paragraph [0130]—This Paragraph [0130] illustrate(s) the antennasinstalled in Carrier CR84. Here, Carrier CR84 may be any carrier ortransportation system designed to carry passenger(s), such asautomobile, motorcycle, railway train, taxi, bus, space ship, or spacestation. In the present embodiment, six antennas, i.e., Antenna Ant84a,Antenna Ant84b, Antenna Ant84c, Antenna Ant84d, Antenna Ant84e, andAntenna Ant84f are installed in Carrier CR84. These antennas send andreceive data in a wireless fashion.

Paragraph [0131]—This Paragraph [0131] illustrate(s) the storage areaincluded in Carrier CR84 (Paragraph [0130]). In the present embodiment,Carrier CR84 includes Station Name Notifying Information Storage AreaCR84a of which the data and the software programs stored therein aredescribed in Paragraph [0132].

Paragraph [0132]—This Paragraph [0132] illustrate(s) the storage areasincluded in Station Name Notifying Information Storage Area CR84a(Paragraph [0131]). In the present embodiment, Station Name NotifyingInformation Storage Area CR84a includes Station Name Notifying DataStorage Area CR84b and Station Name Notifying Software Storage AreaCR84c. Station Name Notifying Data Storage Area CR84b stores the datanecessary to implement the present function on the side of Carrier CR84(Paragraph [0130]), such as the ones described in Paragraph [0133]through Paragraph [0135]. Station Name Notifying Software Storage AreaCR84c stores the software programs necessary to implement the presentfunction on the side of Carrier CR84 (Paragraph [0130]), such as theones described in Paragraph [0136].

Paragraph [0133]—This Paragraph [0133] illustrate(s) the storage areasincluded in Station Name Notifying Data Storage Area CR84b (Paragraph[0132]). In the present embodiment, Station Name Notifying Data StorageArea CR84b includes Station Name Text Data Storage Area CR84b1, StationName Sound Data Storage Area CR84b2, and Work Area CR84b3. Station NameText Data Storage Area CR84b1 stores the data described in Paragraph[0134]. Station Name Sound Data Storage Area CR84b2 stores the datadescribed in Paragraph [0135]. Work Area CR84b3 is utilized as a workarea to perform calculation and temporarily store data.

Paragraph [0134]—This Paragraph [0134] illustrate(s) the data stored inStation Name Text Data Storage Area CR84b1 (Paragraph [0133]). In thepresent embodiment, Station Name Text Data Storage Area CR84b1 comprisestwo columns, i.e., ‘Station Name ID’ and ‘Station Name Text Data’.Column ‘Station Name ID’ stores the station name IDs, and each stationname ID is an identification of the corresponding station name text datastored in column ‘Station Name Text Data’. Column ‘Station Name TextData’ stores the station name text data, and each station name text datais an alphanumeric data indicating the name of the station designed tobe displayed on LCD 201 (FIG. 1). In the present embodiment, StationName Text Data Storage Area CR84b1 stores the following data: thestation name ID ‘Station Name#1’ and the corresponding station name textdata ‘Station Name Text Data#1’; the station name ID ‘Station Name#2’and the corresponding station name text data ‘Station Name Text Data#2’;the station name ID ‘Station Name#3’ and the corresponding station nametext data ‘Station Name Text Data#3’; and the station name ID ‘StationName#4’ and the corresponding station name text data ‘Station Name TextData#4’.

Paragraph [0135]—This Paragraph [0135] illustrate(s) the data stored inStation Name Sound Data Storage Area CR84b2 (Paragraph [0133]). In thepresent embodiment, Station Name Sound Data Storage Area CR84b2comprises two columns, i.e., ‘Station Name ID’ and ‘Station Name SoundData’. Column ‘Station Name ID’ stores the station name IDs, and eachstation name ID is an identification of the corresponding station namesound data stored in column ‘Station Name Sound Data’. The station nameIDs stored in Station Name Sound Data Storage Area CR84b2 are identicalto the ones stored in Station Name Text Data Storage Area CR84b1. Column‘Station Name Sound Data’ stores the station name sound data, and eachstation name sound data is a sound data indicating the name of thestation designed to be output from Speaker 216 (FIG. 1). In the presentembodiment, Station Name Sound Data Storage Area CR84b2 stores thefollowing data: the station name ID ‘Station Name#1’ and thecorresponding station name sound data ‘Station Name Sound Data#1’; thestation name ID ‘Station Name#2’ and the corresponding station namesound data ‘Station Name Sound Data#2’; the station name ID ‘StationName#3’ and the corresponding station name sound data ‘Station NameSound Data#3’; and the station name ID ‘Station Name#4’ and thecorresponding station name sound data ‘Station Name Sound Data#4’. Here,the station name sound data ‘Station Name Sound Data#1’ represents thesound of the station name text data ‘Station Name Text Data#1’ stored inStation Name Text Data Storage Area CR84b1 (Paragraph [0134]); thestation name sound data ‘Station Name Sound Data#2’ represents the soundof the station name text data ‘Station Name Text Data#2’ stored inStation Name Text Data Storage Area CR84b1 (Paragraph [0134]); thestation name sound data ‘Station Name Sound Data#3’ represents the soundof the station name text data ‘Station Name Text Data#3’ stored inStation Name Text Data Storage Area CR84b1 (Paragraph [0134]); and thestation name sound data ‘Station Name Sound Data#4’ represents the soundof the station name text data ‘Station Name Text Data#4’ stored inStation Name Text Data Storage Area CR84b1 (Paragraph [0134]).

Paragraph [0136]—This Paragraph [0136] illustrate(s) the softwareprograms stored in Station Name Notifying Software Storage Area CR84c(Paragraph [0132]). In the present embodiment, Station Name NotifyingSoftware Storage Area CR84c stores Next Station Identifying SoftwareCR84c1 and Station Name Data Sending/Receiving Software CR84c2. NextStation Identifying Software CR84c1 is the software program described inParagraph [0137]. Station Name Data Sending/Receiving Software CR84c2 isthe software program described in Paragraph [0145].

Paragraph [0137]—This Paragraph [0137] illustrate(s) Next StationIdentifying Software CR84c1 (Paragraph [0136]) of Carrier CR84(Paragraph [0130]), which identifies the next station at which CarrierCR84 (Paragraph [0130]) is about to arrive. In the present embodiment,Carrier CR84 (Paragraph [0130]) identifies the next station at whichCarrier CR84 is about to arrive (S1). Carrier CR84 stores the stationname ID of the next station in Work Area CR84b3 (Paragraph [0133]) (S2).

Paragraph [0138]—This Paragraph [0138] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Communication Device 200. In the presentembodiment, RAM 206 includes Station Name Notifying Information StorageArea 20684a of which the data and the software programs stored thereinare described in Paragraph [0140].

Paragraph [0139]—The data and/or the software programs stored in StationName Notifying Information Storage Area 20684a (Paragraph [0138]) may bedownloaded from Host H (Paragraph [0022]) in the manner described inParagraph [0416] through Paragraph [0422].

Paragraph [0140]—This Paragraph [0140] illustrate(s) the storage areasincluded in Station Name Notifying Information Storage Area 20684a(Paragraph [0138]). In the present embodiment, Station Name NotifyingInformation Storage Area 20684a includes Station Name Notifying DataStorage Area 20684b and Station Name Notifying Software Storage Area20684c. Station Name Notifying Data Storage Area 20684b stores the datanecessary to implement the present function on the side of CommunicationDevice 200, such as the ones described in Paragraph [0141] throughParagraph [0143]. Station Name Notifying Software Storage Area 20684cstores the software programs necessary to implement the present functionon the side of Communication Device 200, such as the ones described inParagraph [0144].

Paragraph [0141]—This Paragraph [0141] illustrate(s) the storage areasincluded in Station Name Notifying Data Storage Area 20684b (Paragraph[0140]). In the present embodiment, Station Name Notifying Data StorageArea 20684b includes Station Name Text Data Storage Area 20684b1,Station Name Sound Data Storage Area 20684b2, and Work Area 20684b3.Station Name Text Data Storage Area 20684b1 stores the data described inParagraph [0142]. Station Name Sound Data Storage Area 20684b2 storesthe data described in Paragraph [0143]. Work Area 20684b3 is utilized asa work area to perform calculation and temporarily store data.

Paragraph [0142]—This Paragraph [0142] illustrate(s) the data stored inStation Name Text Data Storage Area 20684b1 (Paragraph [0141]). In thepresent embodiment, Station Name Text Data Storage Area 20684b1comprises two columns, i.e., ‘Station Name ID’ and ‘Station Name TextData’. Column ‘Station Name ID’ stores the station name ID which is anidentification of the corresponding station name text data stored incolumn ‘Station Name Text Data’. Column ‘Station Name Text Data’ storesthe station name text data which is an alphanumeric data designed to bedisplayed on LCD 201 (FIG. 1) indicating the name of the station atwhich Carrier CR84 (Paragraph [0130]) is about to arrive. In the presentembodiment, Station Name Text Data Storage Area 20684b1 stores thefollowing data: the station name ID ‘Station Name#1’ and thecorresponding station name text data ‘Station Name Text Data#1’.

Paragraph [0143]—This Paragraph [0143] illustrate(s) the data stored inStation Name Sound Data Storage Area 20684b2 (Paragraph [0141]). In thepresent embodiment, Station Name Sound Data Storage Area 20684b2comprises two columns, i.e., ‘Station Name Sound ID’ and ‘Station NameSound Data’. Column ‘Station Name Sound ID’ stores the station name IDwhich is an identification of the corresponding station name sound datastored in column ‘Station Name Sound Data’. The station name ID storedin Station Name Sound Data Storage Area CR84b2 (Paragraph [0135]) isidentical to the one stored in Station Name Text Data Storage AreaCR84b1 (Paragraph [0134]). Column ‘Station Name Sound Data’ stores thestation name sound data which is the sound data designed to be outputfrom Speaker 216 (FIG. 1) indicating the name of the station at whichCarrier CR84 (Paragraph [0130]) is about to arrive. In the presentembodiment, Station Name Sound Data Storage Area 20684b2 stores thefollowing data: the station name ID ‘Station Name#1’ and thecorresponding station name sound data ‘Station Name Sound Data#1’. Here,the station name sound data ‘Station Name Sound Data#1’ represents thesound of the station name text data ‘Station Name Text Data#1’ stored inStation Name Text Data Storage Area 20684b1 (Paragraph [0142]).

Paragraph [0144]—This Paragraph [0144] illustrate(s) the softwareprograms stored in Station Name Notifying Software Storage Area 20684c(Paragraph [0140]). In the present embodiment, Station Name NotifyingSoftware Storage Area 20684c stores Station Name Data Sending/ReceivingSoftware 20684c1, Station Name Text Data Notifying Software 20684c2, andStation Name Sound Data Notifying Software 20684c3. Station Name DataSending/Receiving Software 20684c1 is the software program described inParagraph [0145]. Station Name Text Data Notifying Software 20684c2 isthe software program described in Paragraph [0146]. Station Name SoundData Notifying Software 20684c3 is the software program described inParagraph [0147].

Paragraph [0145]—This Paragraph [0145] illustrate(s) Station Name DataSending/Receiving Software CR84c2 (Paragraph [0136]) of Carrier CR84(Paragraph [0130]) and Station Name Data Sending/Receiving Software20684c1 (Paragraph [0144]) of Communication Device 200, which send thestation name text data and the station name sound data to CommunicationDevice 200. In the present embodiment, Carrier CR84 retrieves thestation name ID (e.g., Station Name#1) of the next station from WorkArea CR84b3 (Paragraph [0133]) (S1). Carrier CR84 retrieves thecorresponding station name text data (e.g., Station Name Text Data#1)from Station Name Text Data Storage Area CR84b1 (Paragraph [0134]) (S2).Carrier CR84 retrieves the corresponding station name sound data (e.g.,Station Name Sound Data#1) from Station Name Sound Data Storage AreaCR84b2 (Paragraph [0135]) (S3). Carrier CR84 sends the data retrieved inS1 through S3, which are received by Communication Device 200 viaAntenna 218 (FIG. 1) (S4). CPU 211 (FIG. 1) of Communication Device 200stores the station name ID (e.g., Station Name#1) and the correspondingstation name text data (e.g., Station Name Text Data#1) in Station NameText Data Storage Area 20684b1 (Paragraph [0142]) (S5). CPU 211 storesthe station name ID (e.g., Station Name#1) and the corresponding stationname sound data (e.g., Station Name Sound Data#1) in Station Name SoundData Storage Area 20684b2 (Paragraph [0143]) (S6).

Paragraph [0146]—This Paragraph [0146] illustrate(s) Station Name TextData Notifying Software 20684c2 (Paragraph [0144]) of CommunicationDevice 200, which displays the station name text data on LCD 201 (FIG.1). In the present embodiment, CPU 211 (FIG. 1) of Communication Device200 retrieves the station name text data (e.g., Station Name TextData#1) from Station Name Text Data Storage Area 20684b1 (Paragraph[0142]) (S1) and displays the data on LCD 201 (FIG. 1) (S2). Theforegoing sequence is performed periodically.

Paragraph [0147]—This Paragraph [0147] illustrate(s) Station Name SoundData Notifying Software 20684c3 (Paragraph [0144]) of CommunicationDevice 200, which outputs the station name sound data from Speaker 216(FIG. 1). In the present embodiment, CPU 211 (FIG. 1) of CommunicationDevice 200 retrieves the station name sound data (e.g., Station NameSound Data#1) from Station Name Sound Data Storage Area 20684b2(Paragraph [0143]) (S1) and outputs the data from Speaker 216 (FIG. 1)(S2). The foregoing sequence is performed periodically.

Paragraph [0148]—<<Restaurant eMenu Function>>

Paragraph [0149]—Paragraph [0150] through Paragraph [0183] illustrate(s)the restaurant emenu function which enables the customer of arestaurant, i.e., the user of Communication Device 200, to display therestaurant menu on LCD 201 (FIG. 1) and order menu via CommunicationDevice 200.

Paragraph [0150]—This Paragraph [0150] illustrate(s) the location whereHost H (Paragraph [0022]) is installed. In the present embodiment, HostH is installed in a restaurant, Restaurant Rst85.

Paragraph [0151]—This Paragraph [0151] illustrate(s) the storage areaincluded in Host H (Paragraph [0022]). In the present embodiment, Host Hincludes Restaurant eMenu Information Storage Area H85a of which thedata and the software programs stored therein are described in Paragraph[0152].

Paragraph [0152]—This Paragraph [0152] illustrate(s) the storage areasincluded in Restaurant eMenu Information Storage Area H85a (Paragraph[0151]). In the present embodiment, Restaurant eMenu Information StorageArea H85a includes Restaurant eMenu Text Data Storage Area H85b andRestaurant eMenu Software Storage Area H85c. Restaurant eMenu Text DataStorage Area H85b stores the data necessary to implement the presentfunction on the side of Host H (Paragraph [0022]), such as the onesdescribed in Paragraph [0153] through Paragraph [0163]. Restaurant eMenuSoftware Storage Area H85c stores the software programs necessary toimplement the present function on the side of Host H, such as the onesdescribed in Paragraph [0164].

Paragraph [0153]—This Paragraph [0153] illustrate(s) the storage areasincluded in Restaurant eMenu Text Data Storage Area H85b (Paragraph[0152]). In the present embodiment, Restaurant eMenu Text Data StorageArea H85b includes Menu Text Data Storage Area H85b1, Menu Image DataStorage Area H85b2, Menu Price Data Storage Area H85b3, Selected MenuData Storage Area H85b4, Order Status Data Storage Area H85b5, TotalPrice Data Storage Area H85b6, and Work Area H85b7. Menu Text DataStorage Area H85b1 stores the data described in Paragraph [0154]. MenuImage Data Storage Area H85b2 stores the data described in Paragraph[0155]. Menu Price Data Storage Area H85b3 stores the data described inParagraph [0156]. Selected Menu Data Storage Area H85b4 stores the datadescribed in Paragraph [0157]. Order Status Data Storage Area H85b5stores the data described in Paragraph [0160]. Total Price Data StorageArea H85b6 stores the data described in Paragraph [0163]. Work AreaH85b7 is utilized as a work area to perform calculation and temporarilystore data.

Paragraph [0154]—This Paragraph [0154] illustrate(s) the data stored inMenu Text Data Storage Area H85b1 (Paragraph [0153]). In the presentembodiment, Menu Text Data Storage Area H85b1 comprises two columns,i.e., ‘Menu ID’ and ‘Menu Text Data’. Column ‘Menu ID’ stores the menuIDs, and each menu ID is an identification of the corresponding menutext data stored in column ‘Menu Text Data’. Column ‘Menu Text Data’stores the menu text data, and each menu text data represents the nameof food or beverage. In the present embodiment, Menu Text Data StorageArea H85b1 stores the following data: the menu ID ‘Menu#1’ and thecorresponding menu text data ‘Menu Text Data#1’; the menu ID ‘Menu#2’and the corresponding menu text data ‘Menu Text Data#2’; the menu ID‘Menu#3’ and the corresponding menu text data ‘Menu Text Data#3’; andthe menu ID ‘Menu#4’ and the corresponding menu text data ‘Menu TextData#4’. In the present example, the menu text data ‘Menu Text Data#1’represents ‘corn soup’; the menu text data ‘Menu Text Data#2’ represents‘salad’; the menu text data ‘Menu Text Data#3’ represents ‘beefsteak’;and the menu text data ‘Menu Text Data#4’ represents ‘orange juice’.

Paragraph [0155]—This Paragraph [0155] illustrate(s) the data stored inMenu Image Data Storage Area H85b2 (Paragraph [0153]). In the presentembodiment, Menu Image Data Storage Area H85b2 comprises two columns,i.e., ‘Menu ID’ and ‘Menu Image Data’. Column ‘Menu ID’ stores the menuIDs, and each menu ID is an identification of the corresponding menuimage data stored in column ‘Menu Image Data’. The menu IDs described inthe present embodiment are identical to the ones described in theprevious embodiment. Column ‘Menu Image Data’ stores the menu imagedata, and each menu image data is the image data describing the menutext data stored in Menu Text Data Storage Area H85b1 (Paragraph [0154])of the corresponding menu ID. In the example described in the presentembodiment, Menu Image Data Storage Area H85b2 stores the followingdata: the menu ID ‘Menu#1’ and the corresponding menu image data ‘MenuImage Data#1’; the menu ID ‘Menu#2’ and the corresponding menu imagedata ‘Menu Image Data#2’; the menu ID ‘Menu#3’ and the correspondingmenu image data ‘Menu Image Data#3’; and the menu ID ‘Menu#4’ and thecorresponding menu image data ‘Menu Image Data#4’.

Paragraph [0156]—This Paragraph [0156] illustrate(s) the data stored inMenu Price Data Storage Area H85b3 (Paragraph [0153]). In the presentembodiment, Menu Price Data Storage Area H85b3 comprises two columns,i.e., ‘Menu ID’ and ‘Menu Price Data’. Column ‘Menu ID’ stores the menuIDs, and each menu ID is an identification of the corresponding menuprice data stored in column ‘Menu Price Data’. The menu IDs described inthe present embodiment are identical to the ones described in theprevious two embodiments. Column ‘Menu Price Data’ stores the menu pricedata, and each menu price data indicates the price of the menu of thecorresponding menu ID. In the present embodiment, Menu Price DataStorage Area H85b3 stores the following data: the menu ID ‘Menu#1’ andthe corresponding menu price data ‘Menu Price Data#1’; the menu ID‘Menu#2’ and the corresponding menu price data ‘Menu Price Data#2’; themenu ID ‘Menu#3’ and the corresponding menu price data ‘Menu PriceData#3’; and the menu ID ‘Menu#4’ and the corresponding menu price data‘Menu Price Data#4’. In the present example, the menu price data ‘MenuPrice Data#1’ represents ‘$5’; the menu price data ‘Menu Price Data#2’represents ‘$5’; the menu price data ‘Menu Price Data#3’ represents‘$10’; and the menu price data ‘Menu Price Data#4’ represents ‘$5’.

Paragraph [0157]—This Paragraph [0157] illustrate(s) the data stored inSelected Menu Data Storage Area H85b4 (Paragraph [0153]). In the presentembodiment, Selected Menu Data Storage Area H85b4 comprises two columns,i.e., ‘Order ID’ and ‘Selected Menu Data’. Column ‘Order ID’ stores theorder IDs, and each order ID is an identification of the correspondingselected menu data stored in column ‘Selected Menu Data’. Column‘Selected Menu Data’ stores the selected menu data, and each selectedmenu data includes the data regarding the menu selected by a customer(i.e., the user of Communication Device 200). In the present embodiment,Selected Menu Data Storage Area H85b4 stores the following data: theorder ID ‘Order#1’ and the corresponding selected menu data ‘SelectedMenu Data#1’; the order ID ‘Order#2’ and the corresponding selected menudata ‘Selected Menu Data#2’; the order ID ‘Order#3’ and thecorresponding selected menu data ‘Selected Menu Data#3’; and the orderID ‘Order#4’ and the corresponding selected menu data ‘Selected MenuData#4’.

Paragraph [0158]—This Paragraph [0158] illustrate(s) the selected menudata ‘Selected Menu Data#1’ as an example of the data stored in SelectedMenu Data Storage Area H85b4 (Paragraph [0157]). In the presentembodiment, Selected Menu Data#1 includes the menu IDs ‘Menu#1, Menu#2,and Menu#3’. Referring to the data stored in Menu Text Data Storage AreaH85b1 (Paragraph [0154]), the selected menu data described in thepresent embodiment indicates that a customer (i.e., a user ofCommunication Device 200) represented by the order ID ‘Order#1’ selectedcorn soup, salad, and beefsteak.

Paragraph [0159]—This Paragraph [0159] illustrate(s) the selected menudata ‘Selected Menu Data#2’ as an example of the selected menu datastored in Selected Menu Data Storage Area H85b4 (Paragraph [0157]). Inthe present embodiment, Selected Menu Data#2 includes the menu ID‘Menu#4’. Referring to the data stored in Menu Text Data Storage AreaH85b1 (Paragraph [0154]), the selected menu data described in thepresent embodiment indicates that another customer (i.e., another userof Communication Device 200) represented by the order ID ‘Order#2’selected orange juice.

Paragraph [0160]—This Paragraph [0160] illustrate(s) the data stored inOrder Status Data Storage Area H85b5 (Paragraph [0153]). In the presentembodiment, Order Status Data Storage Area H85b5 comprises two columns,i.e., ‘Order ID’ and ‘Order Status Data’. Column ‘Order ID’ stores theorder IDs, and each order ID is an identification of the correspondingorder status data stored in column ‘Order Status Data’. The order IDsdescribed in the present embodiment are identical to the ones stored inSelected Menu Data Storage Area H85b4 (Paragraph [0157]). Column ‘OrderStatus Data’ stores the order status data, and each order status datarepresents the current status of the order of each food or beverage,i.e., whether the corresponding food or beverage is served to thecorresponding customer or not. In the present embodiment, Order StatusData Storage Area H85b5 stores the following data: the order ID‘Order#1’ and the corresponding order status data ‘Order Status Data#1’;the order ID ‘Order#2’ and the corresponding order status data ‘OrderStatus Data#2’; the order ID ‘Order#3’ and the corresponding orderstatus data ‘Order Status Data#3’; and the order ID ‘Order#4’ and thecorresponding order status data ‘Order Status Data#4’.

Paragraph [0161]—This Paragraph [0161] illustrate(s) the order statusdata ‘Order Status Data#1’ as an example of the data stored in OrderStatus Data Storage Area H85b5 (Paragraph [0160]). In the presentembodiment, Order Status Data#1 includes two columns, i.e., ‘Menu ID’and ‘Status Data’. Column ‘Menu ID’ stores the menu IDs, and each menuID is an identification of the corresponding status data stored incolumn ‘Status Data’. The menu IDs described in the present embodimentare identical to the ones stored in Menu Text Data Storage Area H85b1(Paragraph [0154]). Column ‘Status Data’ stores the status data, andeach status data represents the current status of the order of the foodor beverage of the corresponding menu ID, i.e., whether the food orbeverage of the corresponding menu ID is served to the correspondingcustomer or not. The status data is indicated by either ‘Served’ or NotServed'. In the present embodiment, Order Status Data#1 stores thefollowing data: the menu ID ‘Menu#1’ and the corresponding status data‘Served’; the menu ID ‘Menu#2’ and the corresponding status data‘Served’; and the menu ID ‘Menu#3’ and the corresponding status data NotServed'. The present example indicates that the ordered corn soup isserved, the ordered salad is served, however, the ordered beefsteak isnot yet served.

Paragraph [0162]—This Paragraph [0162] illustrate(s) the order statusdata ‘Order Status Data#2’ as an example of the data stored in OrderStatus Data Storage Area H85b5 (Paragraph [0160]). In the presentembodiment, Order Status Data#2 includes two columns, i.e., ‘Menu ID’and ‘Status Data’. Column ‘Menu ID’ stores the menu IDs, and each menuID is an identification of the corresponding status data stored incolumn ‘Status Data’. The menu IDs described in the present embodimentare identical to the ones stored in Menu Text Data Storage Area H85b1(Paragraph [0154]). Column ‘Status Data’ stores the status data, andeach status data represents the current status of the order of the foodor beverage of the corresponding menu ID, i.e., whether the food orbeverage of the corresponding menu ID is served to the correspondingcustomer or not. The status data is indicated by either ‘Served’ or ‘NotServed’. In the present embodiment, Order Status Data#2 stores thefollowing data: the menu ID ‘Menu#4’ and the corresponding status dataNot Served'. The present example indicates that the ordered orange juiceis not yet served.

Paragraph [0163]—This Paragraph [0163] illustrate(s) the data stored inTotal Price Data Storage Area H85b6 (Paragraph [0153]). In the presentembodiment, Total Price Data Storage Area H85b6 comprises two columns,i.e., ‘Order ID’ and Total Price Data'. Column ‘Order ID’ stores theorder IDs, and each order ID is an identification of the correspondingtotal price data stored in column ‘Total Price Data’. The order IDsdescribed in the present embodiment are identical to the ones stored inSelected Menu Data Storage Area H85b4 (Paragraph [0157]). Column ‘TotalPrice Data’ stores the total price data, and each total price dataindicates the total amount charged to the customer, i.e., the user ofCommunication Device 200, of the corresponding order ID. In the exampledescribed in the present embodiment, Total Price Data Storage Area H85b6stores the following data: the order ID ‘Order#1’ and the correspondingtotal price data ‘Total Price Data#1’; the order ID ‘Order#2’ and thecorresponding total price data ‘Total Price Data#2’; the order ID‘Order#3’ and the corresponding total price data ‘Total Price Data#3’;and the order ID ‘Order#4’ and the corresponding total price data ‘TotalPrice Data#4’. In the present example, the customer represented by theorder ID ‘Order#1’ is charged $25; the customer represented by the orderID ‘Order#2’ is charged $5; the customer represented by the order ID‘Order#3’ is charged $25; and the customer represented by the order ID‘Order#4’ is charged $25.

Paragraph [0164]—This Paragraph [0164] illustrate(s) the softwareprograms stored in Restaurant eMenu Software Storage Area H85c(Paragraph [0152]). In the present embodiment, Restaurant eMenu SoftwareStorage Area H85c stores Menu Data Sending/Receiving Software H85c1,Selected Menu Data Sending/Receiving Software H85c4, Order Status DataUpdating/Notifying Software H85c5, and Total Price DataProducing/Notifying Software H85c6. Menu Data Sending/Receiving SoftwareH85c1 is the software program described in Paragraph [0177]. SelectedMenu Data Sending/Receiving Software H85c4 is the software programdescribed in Paragraph [0181]. Order Status Data Updating/NotifyingSoftware H85c5 is the software program described in Paragraph [0182].Total Price Data Producing/Notifying Software H85c6 is the softwareprogram described in Paragraph [0183].

Paragraph [0165]—This Paragraph [0165] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Communication Device 200. In the presentembodiment, RAM 206 includes Restaurant eMenu Information Storage Area20685a of which the data and the software programs stored therein aredescribed in Paragraph [0166].

Paragraph [0166]—This Paragraph [0166] illustrate(s) the storage areasincluded in Restaurant eMenu Information Storage Area 20685a (Paragraph[0165]). In the present embodiment, Restaurant eMenu Information StorageArea 20685a includes Restaurant eMenu Text Data Storage Area 20685b andRestaurant eMenu Software Storage Area 20685c. Restaurant eMenu TextData Storage Area 20685b stores the data necessary to implement thepresent function on the side of Communication Device 200, such as theones described in Paragraph [0167] through Paragraph [0175]. RestauranteMenu Software Storage Area 20685c stores the software programsnecessary to implement the present function on the side of CommunicationDevice 200, such as the ones described in Paragraph [0176].

Paragraph [0167]—This Paragraph [0167] illustrate(s) the storage areasincluded in Restaurant eMenu Text Data Storage Area 20685b (Paragraph[0166]). In the present embodiment, Restaurant eMenu Text Data StorageArea 20685b includes Menu Text Data Storage Area 20685b1, Menu ImageData Storage Area 20685b2, Menu Price Data Storage Area 20685b3,Selected Menu Data Storage Area 20685b4, Order Status Data Storage Area20685b5, Total Price Data Storage Area 20685b6, and Work Area 20685b7.Menu Text Data Storage Area 20685b1 stores the data described inParagraph [0168]. Menu Image Data Storage Area 20685b2 stores the datadescribed in Paragraph [0169]. Menu Price Data Storage Area 20685b3stores the data described in Paragraph [0170]. Selected Menu DataStorage Area 20685b4 stores the data described in Paragraph [0171].Order Status Data Storage Area 20685b5 stores the data described inParagraph [0173]. Total Price Data Storage Area 20685b6 stores the datadescribed in Paragraph [0175]. Work Area 20685b7 is utilized as a workarea to perform calculation and temporarily store data.

Paragraph [0168]—This Paragraph [0168] illustrate(s) the data stored inMenu Text Data Storage Area 20685b1 (Paragraph [0167]). In the presentembodiment, Menu Text Data Storage Area 20685b1 comprises two columns,i.e., ‘Menu ID’ and ‘Menu Text Data’. Column ‘Menu ID’ stores the menuIDs, and each menu ID is an identification of the corresponding menutext data stored in column ‘Menu Text Data’. Column ‘Menu Text Data’stores the menu text data, and each menu text data represents the nameof food or beverage. In the present embodiment, Menu Text Data StorageArea 20685b1 stores the following data: the menu ID ‘Menu#1’ and thecorresponding menu text data ‘Menu Text Data#1’; the menu ID ‘Menu#2’and the corresponding menu text data ‘Menu Text Data#2’; the menu ID‘Menu#3’ and the corresponding menu text data ‘Menu Text Data#3’; andthe menu ID ‘Menu#4’ and the corresponding menu text data ‘Menu TextData#4’. In the present example, the menu text data ‘Menu Text Data#1’represents ‘corn soup’; the menu text data ‘Menu Text Data#2’ represents‘salad’; the menu text data ‘Menu Text Data#3’ represents ‘beefsteak’;and the menu text data ‘Menu Text Data#4’ represents ‘orange juice’.

Paragraph [0169]—This Paragraph [0169] illustrate(s) the data stored inMenu Image Data Storage Area 20685b2 (Paragraph [0167]). In the presentembodiment, Menu Image Data Storage Area 20685b2 comprises two columns,i.e., ‘Menu ID’ and ‘Menu Image Data’. Column ‘Menu ID’ stores the menuIDs, and each menu ID is an identification of the corresponding menuimage data stored in column ‘Menu Image Data’. The menu IDs described inthe present embodiment are identical to the ones described in theprevious embodiment. Column ‘Menu Image Data’ stores the menu imagedata, and each menu image data is the image data describing the menutext data stored in Menu Text Data Storage Area 20685b1 (Paragraph[0168]) of the corresponding menu ID. In the present embodiment, MenuImage Data Storage Area 20685b2 stores the following data: the menu ID‘Menu#1’ and the corresponding menu image data ‘Menu Image Data#1’; themenu ID ‘Menu#2’ and the corresponding menu image data ‘Menu ImageData#2’; the menu ID ‘Menu#3’ and the corresponding menu image data‘Menu Image Data#3’; and the menu ID ‘Menu#4’ and the corresponding menuimage data ‘Menu Image Data#4’.

Paragraph [0170]—This Paragraph [0170] illustrate(s) the data stored inMenu Price Data Storage Area 20685b3 (Paragraph [0167]). In the presentembodiment, Menu Price Data Storage Area 20685b3 comprises two columns,i.e., ‘Menu ID’ and ‘Menu Price Data’. Column ‘Menu ID’ stores the menuIDs, and each menu ID is an identification of the corresponding menuprice data stored in column ‘Menu Price Data’. The menu IDs described inthe present embodiment are identical to the ones described in theprevious two embodiments. Column ‘Menu Price Data’ stores the menu pricedata, and each menu price data indicates the price of the menu of thecorresponding menu ID. In the present embodiment, Menu Price DataStorage Area 20685b3 stores the following data: the menu ID ‘Menu#1’ andthe corresponding menu price data ‘Menu Price Data#1’; the menu ID‘Menu#2’ and the corresponding menu price data ‘Menu Price Data#2’; themenu ID ‘Menu#3’ and the corresponding menu price data ‘Menu PriceData#3’; and the menu ID ‘Menu#4’ and the corresponding menu price data‘Menu Price Data#4’. In the present example, the menu price data ‘MenuPrice Data#1’ represents ‘$5’; the menu price data ‘Menu Price Data#2’represents ‘$5’; the menu price data ‘Menu Price Data#3’ represents‘$10’; and the menu price data ‘Menu Price Data#4’ represents ‘$5’.

Paragraph [0171]—This Paragraph [0171] illustrate(s) the data stored inSelected Menu Data Storage Area 20685b4 (Paragraph [0167]). In thepresent embodiment, Selected Menu Data Storage Area 20685b4 comprisestwo columns, i.e., ‘Order ID’ and ‘Selected Menu Data’. Column ‘OrderID’ stores the order ID which is an identification of the correspondingselected menu data stored in column ‘Selected Menu Data’. Column‘Selected Menu Data’ stores the selected menu data which includes thedata regarding the menu selected by the customer (i.e., the user ofCommunication Device 200) represented by the order ID ‘Order#1’. In thepresent embodiment, Selected Menu Data Storage Area 20685b4 stores thefollowing data: the order ID ‘Order#1’ and the corresponding selectedmenu data ‘Selected Menu Data#1’.

Paragraph [0172]—This Paragraph [0172] illustrate(s) the selected menudata ‘Selected Menu Data#1’ stored in Selected Menu Data Storage Area20685b4 (Paragraph [0171]). In the present embodiment, Selected MenuData#1 includes the menu IDs ‘Menu#1, Menu#2, and Menu#3’. Referring tothe data stored in Menu Text Data Storage Area 20685b1 (Paragraph[0168]), the selected menu data described in the present embodimentindicates that the customer (i.e., the user of Communication Device 200,for example Device A) represented by the order ID ‘Order#1’ selectedcorn soup, salad, and beefsteak.

Paragraph [0173]—This Paragraph [0173] illustrate(s) the data stored inOrder Status Data Storage Area 20685b5 (Paragraph [0167]). In thepresent embodiment, Order Status Data Storage Area 20685b5 comprises twocolumns, i.e., ‘Order ID’ and ‘Order Status Data’. Column ‘Order ID’stores the order ID which is an identification of the correspondingorder status data stored in column ‘Order Status Data’. The order IDdescribed in the present embodiment is identical to the one stored inSelected Menu Data Storage Area 20685b4 (Paragraph [0171]). Column‘Order Status Data’ stores the order status data which represents thecurrent status of the order of each food or beverage, i.e., whether thecorresponding food or beverage is served to the customer represented bythe order ID ‘Order#1’ or not. In the present embodiment, Order StatusData Storage Area 20685b5 stores the following data: the order ID‘Order#1’ and the corresponding order status data ‘Order Status Data#1’.

Paragraph [0174]—This Paragraph [0174] illustrate(s) the order statusdata ‘Order Status Data#1’ stored in Order Status Data Storage Area20685b5 (Paragraph [0173]). In the present embodiment, Order StatusData#1 includes two columns, i.e., ‘Menu ID’ and ‘Status Data’. Column‘Menu ID’ stores the menu IDs, and each menu ID is an identification ofthe corresponding status data stored in column ‘Status Data’. The menuIDs described in the present embodiment are identical to the ones storedin Menu Text Data Storage Area 20685b1 (Paragraph [0168]). Column‘Status Data’ stores the status data, and each status data representsthe current status of the order of the food or beverage of thecorresponding menu ID, i.e., whether the food or beverage of thecorresponding menu ID is served to the customer represented by the orderID ‘Order#1’ or not. The status data is indicated by either ‘served’ or‘not served’. In the present embodiment, Order Status Data#1 stores thefollowing data: the menu ID ‘Menu#1’ and the corresponding status data‘Served’; the menu ID ‘Menu#2’ and the corresponding status data‘Served’; and the menu ID ‘Menu#3’ and the corresponding status data‘Not Served’. The present example indicates that the ordered corn soupis served, the ordered salad is served, however, the ordered beefsteakis not yet served.

Paragraph [0175]—This Paragraph [0175] illustrate(s) the data stored inTotal Price Data Storage Area 20685b6 (Paragraph [0167]). In the presentembodiment, Total Price Data Storage Area 20685b6 comprises two columns,i.e., ‘Order ID’ and Total Price Data'. Column ‘Order ID’ stores theorder ID which is an identification of the corresponding total pricedata stored in column ‘Total Price Data’. The order ID described in thepresent embodiment is identical to the one stored in Selected Menu DataStorage Area 20685b4 (Paragraph [0171]). Column ‘Total Price Data’stores the total price data which indicates the total amount charged tothe customer, i.e., the user of Communication Device 200, represented bythe order ID ‘Order#1’. In the present embodiment, Total Price DataStorage Area 20685b6 stores the following data: the order ID ‘Order#1’and the corresponding total price data ‘Total Price Data#1’.

Paragraph [0176]—This Paragraph [0176] illustrate(s) the softwareprograms stored in Restaurant eMenu Software Storage Area 20685c(Paragraph [0166]). In the present embodiment, Restaurant eMenu SoftwareStorage Area 20685c stores Menu Data Sending/Receiving Software 20685c1,Menu Data Displaying Software 20685c2, Menu Data Selecting Software20685c3, Selected Menu Data Sending/Receiving Software 20685c4, OrderStatus Data Updating/Notifying Software 20685c5, and Total Price DataProducing/Notifying Software 20685c6. Menu Data Sending/ReceivingSoftware 20685c1 is the software program described in Paragraph [0177].Menu Data Displaying Software 20685c2 is the software program describedin Paragraph [0178]. Menu Data Selecting Software 20685c3 is thesoftware program described in Paragraph [0180]. Selected Menu DataSending/Receiving Software 20685c4 is the software program described inParagraph [0181]. Order Status Data Updating/Notifying Software 20685c5is the software program described in Paragraph [0182]. Total Price DataProducing/Notifying Software 20685c6 is the software program describedin Paragraph [0183].

Paragraph [0177]—This Paragraph [0177] illustrate(s) Menu DataSending/Receiving Software H85c1 (Paragraph [0164]) of Host H (Paragraph[0022]) and Menu Data Sending/Receiving Software 20685c1 (Paragraph[0176]) of Communication Device 200, which transfer the menu data (i.e.,the menu text data, the menu image data, and the menu price data) fromHost H to Communication Device 200 in order to have the menu datadisplayed on LCD 201 (FIG. 1) of Communication Device 200. In thepresent embodiment, CPU 211 (FIG. 1) of Communication Device 200 sends amenu data request, which is received by Host H (S1). Here, the menu datarequest is a signal sent to Host H which requests to send the menu textdata, the menu image data, and the menu price data to CommunicationDevice 200. Host H retrieves all menu IDs and menu text data from MenuText Data Storage Area H85b1 (Paragraph [0154]) (S2). Host H retrievesall menu IDs and menu image data from Menu Image Data Storage Area H85b2(Paragraph [0155]) (S3). Host H retrieves all menu IDs and menu pricedata from Menu Price Data Storage Area H85b3 (Paragraph [0156]) (S4).Host H sends the data retrieved in S2 through S4, which are received byCommunication Device 200 (S5). CPU 211 stores the menu IDs and the menutext data in Menu Text Data Storage Area 20685b1 (Paragraph [0168])(S6). CPU 211 stores the menu IDs and the menu image data in Menu ImageData Storage Area 20685b2 (Paragraph [0169]) (S7). CPU 211 stores themenu IDs and the menu price data in Menu Price Data Storage Area 20685b3(Paragraph [0170]) (S8).

Paragraph [0178]—This Paragraph [0178] illustrate(s) Menu DataDisplaying Software 20685c2 (Paragraph [0176]) of Communication Device200, which displays the menu data (i.e., the menu text data, the menuimage data, and the menu price data) on LCD 201 (FIG. 1) ofCommunication Device 200. In the present embodiment, CPU 211 (FIG. 1) ofCommunication Device 200 retrieves all menu text data from Menu TextData Storage Area 20685b1 (Paragraph [0168]) (S1). CPU 211 retrieves allmenu image data from Menu Image Data Storage Area 20685b2 (Paragraph[0169]) (S2). CPU 211 retrieves all menu price data from Menu Price DataStorage Area 20685b3 (Paragraph [0170]) (S3). CPU 211 displays the dataretrieved in S1 through S3 on LCD 201 (FIG. 1) (S4).

Paragraph [0179]—This Paragraph [0179] illustrate(s) the menu listincluding the menu data (i.e., the menu text data, the menu image data,and the menu price data) displayed on LCD 201 (FIG. 1) of CommunicationDevice 200. In the present embodiment, Menu List ML85 is displayed onLCD 201 (FIG. 1). Menu List ML85 comprises three types of data, i.e.,the menu text data, the menu image data, and the menu price data. In thepresent embodiment, Menu List ML85 comprises the following data: themenu text data ‘Menu Text Data#1’ and the corresponding menu image data‘Menu Image Data#1’ and the corresponding menu price data ‘Menu PriceData#1’; the menu text data ‘Menu Text Data#2’ and the correspondingmenu image data ‘Menu Image Data#2’ and the corresponding menu pricedata ‘Menu Price Data#2’; the menu text data ‘Menu Text Data#3’ and thecorresponding menu image data ‘Menu Image Data#3’ and the correspondingmenu price data ‘Menu Price Data#3’; and the menu text data ‘Menu TextData#4’ and the corresponding menu image data ‘Menu Image Data#4’ andthe corresponding menu price data ‘Menu Price Data#4’.

Paragraph [0180]—This Paragraph [0180] illustrate(s) Menu Data SelectingSoftware 20685c3 (Paragraph [0176]) of Communication Device 200, whichselects a menu from Menu List ML85 described in the previous embodiment.In the present embodiment, the user of Communication Device 200 selectsmenu(s) from Menu List ML85 (S1). CPU 211 (FIG. 1) of CommunicationDevice 200 identifies the corresponding menu IDs (e.g., Menu#1, Menu#2,and Menu#3) (S2). CPU 211 produces the selected menu data (e.g.,Selected Menu Data#1) (S3). Here, the selected menu data is the datarepresenting the menu(s) selected in the previous step. CPU 211 storesthe selected menu data (e.g., Selected Menu Data#1) in Selected MenuData Storage Area 20685b4 (Paragraph [0171]) (S4).

Paragraph [0181]—This Paragraph [0181] illustrate(s) Selected Menu DataSending/Receiving Software H85c4 (Paragraph [0164]) of Host H (Paragraph[0022]) and Selected Menu Data Sending/Receiving Software 20685c4(Paragraph [0176]) of Communication Device 200, which transfer theselected menu data from Communication Device 200 to Host H. In thepresent embodiment, CPU 211 (FIG. 1) of Communication Device 200retrieves the selected menu data (e.g., Selected Menu Data#1) fromSelected Menu Data Storage Area 20685b4 (Paragraph [0171]) (S1). CPU 211sends the selected menu data (e.g., Selected Menu Data#1), which isreceived by Host H (S2). Host H stores the selected menu data (e.g.,Selected Menu Data#1) in Selected Menu Data Storage Area H85b4(Paragraph [0157]) (S3).

Paragraph [0182]—This Paragraph [0182] illustrate(s) Order Status DataUpdating/Notifying Software H85c5 (Paragraph [0164]) of Host H(Paragraph [0022]) and Order Status Data Updating/Notifying Software20685c5 (Paragraph [0176]) of Communication Device 200, which update theorder status data stored in Order Status Data Storage Area H85b5(Paragraph [0160]) of Host H and notifies the customer, i.e., the userof Communication Device 200, of the latest status of his/her order. Inthe present embodiment, the restaurant owner inputs a new order status(e.g., corn soup and salad are served for Order#1) (S1), and Host Hupdates the order status data (e.g., Order Status Data#1) stored inOrder Status Data Storage Area H85b5 (Paragraph [0160]) (S2). Host Hretrieves the updated order status data (e.g., Order Status Data#1) fromOrder Status Data Storage Area H85b5 (Paragraph [0160]), which is sentto Communication Device 200 (S3). CPU 211 (FIG. 1) of CommunicationDevice 200 receives the updated order status data (e.g., Order StatusData#1) from Host H, and stores the data in Order Status Data StorageArea 20685b5 (Paragraph [0173]) (S4). CPU 211 retrieves the updatedorder status data (e.g., Order Status Data#1) from Order Status DataStorage Area 20685b5 (Paragraph [0173]) and displays the data on LCD 201(FIG. 1) (S5).

Paragraph [0183]—This Paragraph [0183] illustrate(s) Total Price DataProducing/Notifying Software H85c6 (Paragraph [0164]) of Host H(Paragraph [0022]) and Total Price Data Producing/Notifying Software20685c6 (Paragraph [0176]) of Communication Device 200, which producethe total price data and notifies the total amount charged to thecustomer, i.e., the user of Communication Device 200, of thecorresponding order ID. In the present embodiment, Host H retrieves theselected menu data (e.g., Selected Menu Data#1) from Selected Menu DataStorage Area H85b4 (Paragraph [0157]) (S1). Host H identifies the menuIDs (e.g., Menu#1, Menu#2, Menu#3) included in Selected Menu Data (e.g.,Selected Menu Data#1) (S2). Host H identifies the menu price data (e.g.,Menu Price Data#1, Menu Price Data#2, Menu Price Data#3) of thecorresponding menu IDs (e.g., Menu#1, Menu#2, Menu#3) (S3). Host Hcalculates the total price data (e.g., Total Price Data#1) from eachmenu price data (e.g., Menu Price Data#1 ($5)+Menu Price Data#2($5)+Menu Price Data#3 ($10)) (S4). Host H stores the total price data(e.g., Total Price Data#1) in Total Price Data Storage Area H85b6(Paragraph [0163]) at the corresponding order ID (e.g., Order#1) (S5).Host H retrieves the total price data (e.g., Total Price Data#1) fromTotal Price Data Storage Area H85b6 (Paragraph [0163]) and sends thedata to Communication Device 200 (S6). CPU 211 (FIG. 1) of CommunicationDevice 200 receives the total price data (e.g., Total Price Data#1) fromHost H and stores the data in Total Price Data Storage Area 20685b6(Paragraph [0175]) (S7). CPU 211 retrieves the total price data (e.g.,Total Price Data#1) from Total Price Data Storage Area 20685b6(Paragraph [0175]) and displays the data on LCD 201 (FIG. 1) (S8).

Paragraph [0184]—<<Geographic Location Recording Function>>

Paragraph [0185]—Paragraph [0186] through Paragraph [0219] illustrate(s)the geographic location recording function which records the geographiclocation of Device A, a Communication Device 200, and/or Device B,another Communication Device 200. Assume that user A owns Device A, aCommunication Device 200, and user B owns Device B, anotherCommunication Device 200.

Paragraph [0186]—This Paragraph [0186] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Device A. In the present embodiment, RAM206 includes Geographic Location Recording Information Storage Area20686aA of which the data and the software programs stored therein aredescribed in Paragraph [0188].

Paragraph [0187]—The data and/or the software programs stored inGeographic Location Recording Information Storage Area 20686aA(Paragraph [0186]) may be downloaded from Host H (Paragraph [0022]) inthe manner described in Paragraph [0416] through Paragraph [0422].

Paragraph [0188]—This Paragraph [0188] illustrate(s) the storage areasincluded in Geographic Location Recording Information Storage Area20686aA (Paragraph [0186]). In the present embodiment, GeographicLocation Recording Information Storage Area 20686aA includes GeographicLocation Recording Data Storage Area 20686bA and Geographic LocationRecording Software Storage Area 20686cA. Geographic Location RecordingData Storage Area 20686bA stores the data necessary to implement thepresent function on the side of Device A, such as the ones described inParagraph [0189] through Paragraph [0194]. Geographic Location RecordingSoftware Storage Area 20686cA stores the software programs necessary toimplement the present function on the side of Device A, such as the onesdescribed in Paragraph [0195].

Paragraph [0189]—This Paragraph [0189] illustrate(s) the storage areasincluded in Geographic Location Recording Data Storage Area 20686bA(Paragraph [0188]). In the present embodiment, Geographic LocationRecording Data Storage Area 20686bA includes Device A's Location DataStorage Area 20686b1A, Device B's Location Data Storage Area 20686b2A,3D Map Data Storage Area 20686b3A, Street Address Location Storage Area20686b4A, Phone Number Location Storage Area 20686b5A, Icon Image DataStorage Area 20686b6A, and Work Area 20686b7A. Device A's Location DataStorage Area 20686b1A stores the data described in Paragraph [0190].Device B's Location Data Storage Area 20686b2A stores the data describedin Paragraph [0191]. 3D Map Data Storage Area 20686b3A stores the 3D mapdata. Here, the 3D map data is a map data covering the entire nationcomposed of a plurality of three-dimensional data. Street AddressLocation Storage Area 20686b4A stores the data described in Paragraph[0192]. Phone Number Location Storage Area 20686b5A stores the datadescribed in Paragraph [0193]. Icon Image Data Storage Area 20686b6Astores the data described in Paragraph [0194]. Work Area 20686b7A isutilized as a work area to perform calculation and temporarily storedata.

Paragraph [0190]—This Paragraph [0190] illustrate(s) the data stored inDevice A's Location Data Storage Area 20686b1A (Paragraph [0189]). Inthe present embodiment, Device A's Location Data Storage Area 20686b1Acomprises two columns, i.e., ‘Time Data’ and ‘Device A's Location Data’.Column ‘Time Data’ stores the time data, and each time data is anidentification of the Device A's location data stored in column DeviceA's Location Data'. Each time data represents the time at which thecorresponding Device A's location data is stored in Device A's LocationData Storage Area 20686b1A. The time data is stored in(yyyy/mm/dd/hh/mm/ss) format, wherein ‘yyyy’ represents the year, ‘mm’represents the month ‘dd’ represents the day, ‘hh’ represents the hour,‘mm’ represents the minute, and ‘ss’ represents the second. Column‘Device A's Location Data’ stores the Device A's location data, and eachDevice A's location data represents the geographic location in (x,y,z)format of Device A at the time indicated by the corresponding time data.In the present embodiment, Device A's Location Data Storage Area20686b1A stores the following data: the time data ‘Time Data#1’ and thecorresponding Device A's location data ‘Device A's Location Data#1; thetime data Time Data#2’ and the corresponding Device A's location data‘Device A's Location Data#2’; the time data ‘Time Data#3’ and thecorresponding Device A's location data ‘Device A's Location Data#3’; andthe time data ‘Time Data#4’ and the corresponding Device A's locationdata ‘Device A's Location Data#4’.

Paragraph [0191]—This Paragraph [0191] illustrate(s) the data stored inDevice B's Location Data Storage Area 20686b2A (Paragraph [0189]). Inthe present embodiment, Device B's Location Data Storage Area 20686b2Acomprises two columns, i.e., ‘Time Data’ and ‘Device B's Location Data’.Column ‘Time Data’ stores the time data, and each time data is anidentification of the Device B's location data stored in column ‘DeviceB's Location Data’. Each time data represents the time at which thecorresponding Device B's location data is stored in Device B's LocationData Storage Area 20686b2A. The time data is stored in(yyyy/mm/dd/hh/mm/ss) format, wherein ‘yyyy’ represents the year, ‘mm’represents the month ‘dd’ represents the day, ‘hh’ represents the hour,‘mm’ represents the minute, and ‘ss’ represents the second. Column‘Device B's Location Data’ stores the Device B's location data, and eachDevice B's location data represents the geographic location in (x,y,z)format of Device B at the time indicated by the corresponding time data.In the present embodiment, Device B's Location Data Storage Area20686b2A stores the following data: the time data ‘Time Data#5’ and thecorresponding Device B's location data ‘Device B's Location Data#5’; thetime data ‘Time Data#6’ and the corresponding Device B's location data‘Device B's Location Data#6’; the time data ‘Time Data#7’ and thecorresponding Device B's location data ‘Device B's Location Data#7’; andthe time data ‘Time Data#8’ and the corresponding Device B's locationdata ‘Device B's Location Data#8’.

Paragraph [0192]—This Paragraph [0192] illustrate(s) the data stored inStreet Address Location Storage Area 20686b4A (Paragraph [0189]). In thepresent embodiment, Street Address Location Storage Area 20686b4Acomprises two columns, i.e., ‘Street Address Data’ and ‘Street AddressLocation Data’. Column ‘Street Address Data’ stores the street addressdata, and each street address data represents a street address. Thestreet address data includes the name of the state, the name of county,the name of street, and/or the street number. Column ‘Street AddressLocation Data’ stores the street address location data, and each streetaddress location data represents the geographic location in (x,y,z)format of the corresponding street address data. In the presentembodiment, Street Address Location Storage Area 20686b4A stores thefollowing data: the street address data ‘Street Address Data#1’ and thecorresponding street address location data ‘Street Address LocationData#1’; the street address data ‘Street Address Data#2’ and thecorresponding street address location data ‘Street Address LocationData#2’; the street address data ‘Street Address Data#3’ and thecorresponding street address location data ‘Street Address LocationData#3’; and the street address data ‘Street Address Data#4’ and thecorresponding street address location data ‘Street Address LocationData#4’.

Paragraph [0193]—This Paragraph [0193] illustrate(s) the data stored inPhone Number Location Storage Area 20686b5A (Paragraph [0189]). In thepresent embodiment, Phone Number Location Storage Area 20686b5Acomprises two columns, i.e., ‘Phone Number Data’ and ‘Phone NumberLocation Data’. Column ‘Phone Number Data’ stores the phone number data,and each phone number data represents a phone number. Column ‘PhoneNumber Location Data’ stores the phone number location data, and eachphone number location data represents the geographic location of thepremises (e.g., a restaurant or a hotel) in (x,y,z) format at which thecorresponding phone number data is utilized. In the present embodiment,Phone Number Location Storage Area 20686b5A stores the following data:the phone number data ‘Phone Number Data#1’ and the corresponding phonenumber location data ‘Phone Number Location Data#1’; the phone numberdata ‘Phone Number Data#2’ and the corresponding phone number locationdata ‘Phone Number Location Data#2’; the phone number data ‘Phone NumberData#3’ and the corresponding phone number location data ‘Phone NumberLocation Data#3’; and the phone number data ‘Phone Number Data#4’ andthe corresponding phone number location data ‘Phone Number LocationData#4’.

Paragraph [0194]—This Paragraph [0194] illustrate(s) the data stored inIcon Image Data Storage Area 20686b6A (Paragraph [0189]). In the presentembodiment, Icon Image Data Storage Area 20686b6A comprises two columns,i.e., ‘Icon Image ID’ and Icon Image Data'. Column ‘Icon Image ID’stores the icon image IDs, and each icon image ID is an identificationof the corresponding icon image data stored in column ‘Icon Image Data’.Column ‘Icon Image Data’ stores the icon image data, and each icon imagedata is an image data designed to be displayed on LCD 201 (FIG. 1)indicating the geographic location of Device A or Device B. In thepresent embodiment, Icon Image Data Storage Area 20686b6A stores thefollowing data: the icon image ID ‘Icon Image#1’ and the correspondingicon image data ‘Icon Image Data#1’; and the icon image ID ‘IconImage#2’ and the corresponding icon image data ‘Icon Image Data#2’. Inthe present example, the icon image data ‘Icon Image Data#1’ representsDevice A and the icon image data ‘Icon Image Data#2’ represents DeviceB.

Paragraph [0195]—This Paragraph [0195] illustrate(s) the softwareprograms stored in Geographic Location Recording Software Storage Area20686cA (Paragraph [0188]). In the present embodiment, GeographicLocation Recording Software Storage Area 20686cA stores Device A'sLocation One Time Recording Software 20686c1A, Device A's LocationContinuous Recording Software 20686c2A, Device A's Location DisplayingSoftware 20686c3A, Device A's Location Replaying Software 20686c4A,Device A's Location Street Address Displaying Software 20686c5A, DeviceA's Location Phone Number Displaying Software 20686c6A, Device A'sLocation Information Sending/Receiving Software 20686c7A, Device B'sLocation One Time Recording Software 20686c8A, Device B's LocationContinuous Recording Software 20686c9A, Device B's Location DisplayingSoftware 20686c10A, Device B's Location Replaying Software 20686c11A,Device B's Location Street Address Displaying Software 20686c12A, DeviceB's Location Phone Number Displaying Software 20686c13A, and Device B'sLocation Information Sending/Receiving Software 20686c14A. Device A'sLocation One Time Recording Software 20686c1A is the software programdescribed in Paragraph [0206]. Device A's Location Continuous RecordingSoftware 20686c2A is the software program described in Paragraph [0207].Device A's Location Displaying Software 20686c3A is the software programdescribed in Paragraph [0208]. Device A's Location Replaying Software20686c4A is the software program described in Paragraph [0209]. DeviceA's Location Street Address Displaying Software 20686c5A is the softwareprogram described in Paragraph [0210]. Device A's Location Phone NumberDisplaying Software 20686c6A is the software program described inParagraph [0211]. Device A's Location Information Sending/ReceivingSoftware 20686c7A is the software program described in Paragraph [0212].Device B's Location One Time Recording Software 20686c8A is the softwareprogram described in Paragraph [0213]. Device B's Location ContinuousRecording Software 20686c9A is the software program described inParagraph [0214]. Device B's Location Displaying Software 20686c10A isthe software program described in Paragraph [0215]. Device B's LocationReplaying Software 20686c11A is the software program described inParagraph [0216]. Device B's Location Street Address Displaying Software20686c12A is the software program described in Paragraph [0217]. DeviceB's Location Phone Number Displaying Software 20686c13A is the softwareprogram described in Paragraph [0218]. Device B's Location InformationSending/Receiving Software 20686c14A is the software program describedin Paragraph [0205].

Paragraph [0196]—This Paragraph [0196] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Device B. In the present embodiment, RAM206 includes Geographic Location Recording Information Storage Area20686aB of which the data and the software programs stored therein aredescribed in Paragraph [0198].

Paragraph [0197]—The data and/or the software programs stored inGeographic Location Recording Information Storage Area 20686aB(Paragraph [0196]) may be downloaded from Host H (Paragraph [0022]) inthe manner described in Paragraph [0416] through Paragraph [0422].

Paragraph [0198]—This Paragraph [0198] illustrate(s) the storage areasincluded in Geographic Location Recording Information Storage Area20686aB (Paragraph [0196]). In the present embodiment, GeographicLocation Recording Information Storage Area 20686aB includes GeographicLocation Recording Data Storage Area 20686bB and Geographic LocationRecording Software Storage Area 20686cB. Geographic Location RecordingData Storage Area 20686bB stores the data necessary to implement thepresent function on the side of Device B, such as the ones described inParagraph [0199] through Paragraph [0204]. Geographic Location RecordingSoftware Storage Area 20686cB stores the software programs necessary toimplement the present function on the side of Device B, such as the onesdescribed in Paragraph [0205].

Paragraph [0199]—This Paragraph [0199] illustrate(s) the storage areasincluded in Geographic Location Recording Data Storage Area 20686bB(Paragraph [0198]). As described in the present embodiment, GeographicLocation Recording Data Storage Area 20686bB includes Device B'sLocation Data Storage Area 20686b1B, Device A's Location Data StorageArea 20686b2B, 3D Map Data Storage Area 20686b3B, Street AddressLocation Storage Area 20686b4B, Phone Number Location Storage Area20686b5B, Icon Image Data Storage Area 20686b6B, and Work Area 20686b7B.Device B's Location Data Storage Area 20686b1B stores the data describedin Paragraph [0200]. Device A's Location Data Storage Area 20686b2Bstores the data described in Paragraph [0201]. 3D Map Data Storage Area20686b3B stores the 3D map data. Here, the 3D map data is a map datacovering the entire nation composed of a plurality of three-dimensionaldata. Street Address Location Storage Area 20686b4B stores the datadescribed in Paragraph [0202]. Phone Number Location Storage Area20686b5B stores the data described in Paragraph [0203]. Icon Image DataStorage Area 20686b6B stores the data described in Paragraph [0204].Work Area 20686b7B is utilized as a work area to perform calculation andtemporarily store data.

Paragraph [0200]—This Paragraph [0200] illustrate(s) the data stored inDevice B's Location Data Storage Area 20686b1B (Paragraph [0199]). Inthe present embodiment, Device B's Location Data Storage Area 20686b1Bcomprises two columns, i.e., ‘Time Data’ and ‘Device B's Location Data’.Column ‘Time Data’ stores the time data, and each time data is anidentification of the Device B's location data stored in column ‘DeviceB's Location Data’. Each time data represents the time at which thecorresponding Device B's location data is stored in Device B's LocationData Storage Area 20686b1B. The time data is stored in(yyyy/mm/dd/hh/mm/ss) format, wherein ‘yyyy’ represents the year, ‘mm’represents the month ‘dd’ represents the day, ‘hh’ represents the hour,‘mm’ represents the minute, and ‘ss’ represents the second. Column‘Device B's Location Data’ stores the Device B's location data, and eachDevice B's location data represents the geographic location in (x,y,z)format of Device B at the time indicated by the corresponding time data.In the present embodiment, Device B's Location Data Storage Area20686b1B stores the following data: the time data ‘Time Data#5’ and thecorresponding Device B's location data ‘Device B's Location Data#5’; thetime data ‘Time Data#6’ and the corresponding Device B's location data‘Device B's Location Data#6’; the time data ‘Time Data#7’ and thecorresponding Device B's location data ‘Device B's Location Data#7’; andthe time data ‘Time Data#8’ and the corresponding Device B's locationdata ‘Device B's Location Data#8’.

Paragraph [0201]—This Paragraph [0201] illustrate(s) the data stored inDevice A's Location Data Storage Area 20686b2B (Paragraph [0199]). Inthe present embodiment, Device A's Location Data Storage Area 20686b2Bcomprises two columns, i.e., ‘Time Data’ and ‘Device A's Location Data’.Column ‘Time Data’ stores the time data, and each time data is anidentification of the Device A's location data stored in column ‘DeviceA's Location Data’. Each time data represents the time at which thecorresponding Device A's location data is stored in Device A's LocationData Storage Area 20686b2B. The time data is stored in(yyyy/mm/dd/hh/mm/ss) format, wherein ‘yyyy’ represents the year, ‘mm’represents the month ‘dd’ represents the day, ‘hh’ represents the hour,‘mm’ represents the minute, and ‘ss’ represents the second. Column‘Device A's Location Data’ stores the Device A's location data, and eachDevice A's location data represents the geographic location in (x,y,z)format of Device A at the time indicated by the corresponding time data.In the present embodiment, Device A's Location Data Storage Area20686b2B stores the following data: the time data ‘Time Data#1’ and thecorresponding Device A's location data ‘Device A's Location Data#1’; thetime data ‘Time Data#2’ and the corresponding Device A's location data‘Device A's Location Data#2’; the time data ‘Time Data#3’ and thecorresponding Device A's location data ‘Device A's Location Data#3’; andthe time data ‘Time Data#4’ and the corresponding Device A's locationdata ‘Device A's Location Data#4’.

Paragraph [0202]—This Paragraph [0202] illustrate(s) the data stored inStreet Address Location Storage Area 20686b4B (Paragraph [0199]). In thepresent embodiment, Street Address Location Storage Area 20686b4Bcomprises two columns, i.e., ‘Street Address Data’ and ‘Street AddressLocation Data’. Column ‘Street Address Data’ stores the street addressdata, and each street address data represents a street address. Thestreet address data includes the name of state, the name of county, thename of street, and/or the street number. Column ‘Street AddressLocation Data’ stores the street address location data, and each streetaddress location data represents the geographic location in (x,y,z)format of the corresponding street address data. In the presentembodiment, Street Address Location Storage Area 20686b4B stores thefollowing data: the street address data ‘Street Address Data#1’ and thecorresponding street address location data ‘Street Address LocationData#1’; the street address data ‘Street Address Data#2’ and thecorresponding street address location data ‘Street Address LocationData#2’; the street address data ‘Street Address Data#3’ and thecorresponding street address location data ‘Street Address LocationData#3’; and the street address data ‘Street Address Data#4’ and thecorresponding street address location data ‘Street Address LocationData#4’.

Paragraph [0203]—This Paragraph [0203] illustrate(s) the data stored inPhone Number Location Storage Area 20686b5B (Paragraph [0199]). In thepresent embodiment, Phone Number Location Storage Area 20686b5Bcomprises two columns, i.e., ‘Phone Number Data’ and ‘Phone NumberLocation Data’. Column ‘Phone Number Data’ stores the phone number data,and each phone number data represents a phone number. Column ‘PhoneNumber Location Data’ stores the phone number location data, and eachphone number location data represents the geographic location of thepremises (e.g., a restaurant or a hotel) in (x,y,z) format at which thecorresponding phone number data is utilized. In the present embodiment,Phone Number Location Storage Area 20686b5B stores the following data:the phone number data ‘Phone Number Data#1’ and the corresponding phonenumber location data ‘Phone Number Location Data#1’; the phone numberdata ‘Phone Number Data#2’ and the corresponding phone number locationdata ‘Phone Number Location Data#2’; the phone number data ‘Phone NumberData#3’ and the corresponding phone number location data ‘Phone NumberLocation Data#3’; and the phone number data ‘Phone Number Data#4’ andthe corresponding phone number location data ‘Phone Number LocationData#4’.

Paragraph [0204]—This Paragraph [0204] illustrate(s) the data stored inIcon Image Data Storage Area 20686b6B (Paragraph [0199]). In the presentembodiment, Icon Image Data Storage Area 20686b6B comprises two columns,i.e., ‘Icon Image ID’ and ‘Icon Image Data’. Column ‘Icon Image ID’stores the icon image IDs, and each icon image ID is an identificationof the corresponding icon image data stored in column ‘Icon Image Data’.Column ‘Icon Image Data’ stores the icon image data, and each icon imagedata is an image data designed to be displayed on LCD 201 (FIG. 1)indicating the geographic location of Device A or Device B. In theexample described in the present embodiment, Icon Image Data StorageArea 20686b6B stores the following data: the icon image ID ‘IconImage#1’ and the corresponding icon image data ‘Icon Image Data#1’; theicon image ID ‘Icon Image#2’ and the corresponding icon image data ‘IconImage Data#2’; and In the present example, the icon image data ‘IconImage Data#1’ represents Device A and the icon image data ‘Icon ImageData#2’ represents Device B.

Paragraph [0205]—This Paragraph [0205] illustrate(s) the softwareprograms stored in Geographic Location Recording Software Storage Area20686cB (Paragraph [0198]). In the present embodiment, GeographicLocation Recording Software Storage Area 20686cB stores Device B'sLocation One Time Recording Software 20686c1B, Device B's LocationContinuous Recording Software 20686c2B, Device B's Location DisplayingSoftware 20686c3B, Device B's Location Replaying Software 20686c4B,Device B's Location Street Address Displaying Software 20686c5B, DeviceB's Location Phone Number Displaying Software 20686c6B, Device B'sLocation Information Sending Software 20686c7B, Device A's Location OneTime Recording Software 20686c8B, Device A's Location ContinuousRecording Software 20686c9B, Device A's Location Displaying Software20686c10B, Device A's Location Replaying Software 20686c11B, Device A'sLocation Street Address Displaying Software 20686c12B, Device A'sLocation Phone Number Displaying Software 20686c13B, and Device A'sLocation Information Sending/Receiving Software 20686c14B. Device B'sLocation One Time Recording Software 20686c1B is the software programdescribed in Paragraph [0213]. Device B's Location Continuous RecordingSoftware 20686c2B is the software program described in Paragraph [0214].The sequence of Device B's Location Displaying Software 20686c3B issimilar to the sequence of Device A's Location Displaying Software20686c3A (Paragraph [0208]). The sequence of Device B's LocationReplaying Software 20686c4B is similar to the sequence of Device A'sLocation Replaying Software 20686c4A (Paragraph [0209]). The sequence ofDevice B's Location Street Address Displaying Software 20686c5B issimilar to the sequence of Device A's Location Street Address DisplayingSoftware 20686c5A (Paragraph [0210]). The sequence of Device B'sLocation Phone Number Displaying Software 20686c6B is similar to thesequence of Device A's Location Phone Number Displaying Software20686c6A (Paragraph [0211]). Device A's Location One Time RecordingSoftware 20686c8B is the software program described in Paragraph [0206].Device A's Location Continuous Recording Software 20686c9B is thesoftware program described in Paragraph [0207]. The sequence of DeviceA's Location Displaying Software 20686c10B is similar to the sequence ofDevice B's Location Displaying Software 20686c10A (Paragraph [0215]).The sequence of Device A's Location Replaying Software 20686c11B issimilar to the sequence of Device B's Location Replaying Software20686c11A (Paragraph [0216]). The sequence of Device A's Location StreetAddress Displaying Software 20686c12B is similar to the sequence ofDevice B's Location Street Address Displaying Software 20686c12A(Paragraph [0217]). The sequence of Device A's Location Phone NumberDisplaying Software 20686c13B is similar to the sequence of Device B'sLocation Phone Number Displaying Software 20686c13A (Paragraph [0218]).The sequence of Device A's Location Info Sending/Receiving Software20686c14B is similar to the sequence of Device B's Location InfoSending/Receiving Software 20686c14A.

Paragraph [0206]—This Paragraph [0206] illustrate(s) Device A's LocationOne Time Recording Software 20686c1A (Paragraph [0195]) of Device A andDevice A's Location One Time Recording Software 20686c8B (Paragraph[0205]) of Device B, which store the current location of Device A forone time. In the present embodiment, the user of Device A inputs aDevice A's location one time recording signal (S1). Here, the Device A'slocation one time recording signal is a signal which instructs CPU 211(FIG. 1) of Device A to initiate implementing the following steps. CPU211 (FIG. 1) of Device A identifies the current time and stores the datain column ‘Time Data’ (e.g., Time Data#1) of Device A's Location DataStorage Area 20686b1A (Paragraph [0190]) (S2). CPU 211 of Device Aidentifies the current geographic location data of Device A and storesthe data in column ‘Device A's Location Data’ (e.g., Device A's LocationData#1) of Device A's Location Data Storage Area 20686b1A (Paragraph[0190]) (S3). CPU 211 of Device A retrieves the time data and the DeviceA's location data from Device A's Location Data Storage Area 20686b1A(Paragraph [0190]) and sends the data to Device B via Antenna 218(FIG. 1) (S4). CPU 211 of Device B receives the time data and the DeviceA's location data from Device A and stores the data in Device A'sLocation Data Storage Area 20686b2B (Paragraph [0201]) (S5).

Paragraph [0207]—This Paragraph [0207] illustrate(s) Device A's LocationContinuous Recording Software 20686c2A (Paragraph [0195]) of Device Aand Device A's Location Continuous Recording Software 20686c9B(Paragraph [0205]) of Device B, which continuously store the currentlocation of Device A. In the present embodiment, the user of Device Ainputs a Device A's location continuous recording signal (Device A)(S1). Here, the Device A's location continuous recording signal is asignal which instructs CPU 211 (FIG. 1) of Device A to initiateimplementing the following steps. CPU 211 of Device A identifies thecurrent time and adds the data as a new time data in column ‘Time Data’(e.g., Time Data#1) of Device A's Location Data Storage Area 20686b1A(Paragraph [0190]) (S2). CPU 211 of Device A identifies the currentgeographic location data of Device A and adds the data as a new DeviceA's location data in column ‘Device A's Location Data’ (e.g., Device A'sLocation Data#1) of Device A's Location Data Storage Area 20686b1A(Paragraph [0190]) (S3). CPU 211 of Device A retrieves the new time dataand Device A's location data from Device A's Location Data Storage Area20686b1A (Paragraph [0190]) and sends the data to Device B via Antenna218 (FIG. 1) (S4). The sequence of S2 through S4 is repeatedPeriodically (S5).

Paragraph [0208]—This Paragraph [0208] illustrate(s) Device A's LocationDisplaying Software 20686c3A (Paragraph [0195]) of Device A, whichdisplays the current location of Device A on LCD 201 (FIG. 1) of DeviceA. In the present embodiment, CPU 211 (FIG. 1) of Device A retrieves alltime data from Device A's Location Data Storage Area 20686b1A (Paragraph[0190]) and displays a list of time data on LCD 201 (FIG. 1) (S1). Theuser of Device A selects a time data (e.g., Time Data#1) by utilizingInput Device 210 (FIG. 1) or via voice recognition system (S2). CPU 211of Device A retrieves the corresponding Device A's location data (e.g.,Device A's Location Data#1) (S3). CPU 211 of Device A retrieves the 3Dmap data from 3D Map Data Storage Area 20686b3A and displays the data onLCD 201 (FIG. 1) of Device A (S4). CPU 211 of Device A retrieves IconImage Data#1 from Icon Image Data Storage Area 20686b6A (Paragraph[0194]) (S5), and displays the data on LCD 201 of Device A at thelocation corresponding to the Device A's location data (e.g., Device A'sLocation Data#1) retrieved in S3 (S6).

Paragraph [0209]—This Paragraph [0209] illustrate(s) Device A's LocationReplaying Software 20686c4A (Paragraph [0195]) of Device A, whichreplays the location of Device A. In the present embodiment, CPU 211(FIG. 1) of Device A retrieves the 3D map from 3D Map Data Storage Area20686b3A and the data is displayed on LCD 201 (FIG. 1) of Device A (S1).CPU 211 of Device A retrieves the 1st time data (e.g., Time Data#1)stored in Device A's Location Data Storage Area 20686b1A (Paragraph[0190]) (S2). CPU 211 of Device A retrieves the corresponding Device A'slocation data (e.g., Device A's Location Data#1) (S3). CPU 211 of DeviceA retrieves Icon Image Data#1 from Icon Image Data Storage Area 20686b6A(Paragraph [0194]) (S4), and displays the data on LCD 201 of Device A atthe location corresponding to Device A's location data (e.g., Device A'sLocation Data#1) retrieved in S3 (S5). The sequence of S2 through S5 isperformed with the 2nd time data (e.g., Time Data#2), the 3rd time data(e.g., Time Data#3), and the 4th time data (e.g., Time Data#4) (S6).

Paragraph [0210]—This Paragraph [0210] illustrate(s) Device A's LocationStreet Address Displaying Software 20686c5A (Paragraph [0195]) of DeviceA, which displays the street address of the premises (e.g., a hotel or arestaurant) where Device A is currently located. In the presentembodiment, CPU 211 of Device A retrieves all time data from Device A'sLocation Data Storage Area 20686b1A (Paragraph [0190]) and displays alist of time data on LCD 201 (FIG. 1) of Device A (S1). The user ofDevice A selects a time data (e.g., Time Data#1) by utilizing InputDevice 210 (FIG. 1) or via voice recognition system (S2). CPU 211 ofDevice A retrieves the corresponding Device A's location data (e.g.,Device A's Location Data#1) (S3). CPU 211 of Device A identifies theclosest street address location data (e.g., Street Address LocationData#1) stored in Street Address Location Storage Area 20686b4A(Paragraph [0192]) (S4). CPU 211 of Device A retrieves the correspondingstreet address data (e.g., Street Address Data#1) from Street AddressLocation Storage Area 20686b4A (Paragraph [0192]) and displays the dataon LCD 201 (FIG. 1) of Device A (S5).

Paragraph [0211]—This Paragraph [0211] illustrate(s) Device A's LocationPhone Number Displaying Software 20686c6A (Paragraph [0195]) of DeviceA, which displays the phone number of the premises (e.g., a hotel orrestaurant) where Device A is currently located. In the presentembodiment, CPU 211 (FIG. 1) of Device A retrieves all time data fromDevice A's Location Data Storage Area 20686b1A (Paragraph [0190]) anddisplays a list of time data on LCD 201 (FIG. 1) of Device A (S1). Theuser of Device A selects a time data (e.g., Time Data#1) by utilizingInput Device 210 (FIG. 1) or via voice recognition system (S2). CPU 211of Device A retrieves the corresponding Device A's location data (e.g.,Device A's Location Data#1) (S3). CPU 211 of Device A identifies theclosest phone number location data (e.g., Phone Number Location Data#1)stored in Phone Number Location Storage Area 20686b5A (Paragraph [0193])(S4). CPU 211 of Device A retrieves the corresponding phone number data(e.g., Phone Number Data#1) from Phone Number Location Storage Area20686b5A (Paragraph [0193]) and displays the data on LCD 201 (FIG. 1) ofDevice A (S5).

Paragraph [0212]—This Paragraph [0212] illustrate(s) Device A's LocationInformation Sending/Receiving Software 20686c7A (Paragraph [0195]) ofDevice A and Device A's Location Information Sending Software 20686cB(Paragraph [0205]) of Device B, which send the Device A's location data,the Device A's location street address, and the Device A's locationphone number to Device B. In the present embodiment, CPU 211 of Device Aretrieves all time data from Device A's Location Data Storage Area20686b1A (Paragraph [0190]) and displays a list of time data on LCD 201(FIG. 1) of Device A (S1). The user of Device A selects a time data(e.g., Time Data#1) by utilizing Input Device 210 (FIG. 1) or via voicerecognition system (S2). CPU 211 of Device A retrieves the correspondingDevice A's location data (e.g., Device A's Location Data#1) (S3). CPU211 of Device A identifies the closest street address location data(e.g., Street Address Location Data#1) stored in Street Address LocationStorage Area 20686b4A (Paragraph [0192]) (S4). CPU 211 of Device Aretrieves the corresponding street address data (e.g., Street AddressData#1) from Street Address Location Storage Area 20686b4A (Paragraph[0192]) and displays the data on LCD 201 (FIG. 1) of Device A (S5). CPU211 of Device A identifies the closest phone number location data (e.g.,Phone Number Location Data#1) stored in Phone Number Location StorageArea 20686b5A (Paragraph [0193]) (S6). CPU 211 of Device A retrieves thecorresponding phone number data (e.g., Phone Number Data#1) from PhoneNumber Location Storage Area 20686b5A (Paragraph [0193]) and displaysthe data on LCD 201 (FIG. 1) of Device A (S7). CPU 211 of Device A sendsthe Device A's location data, the Device A's location street address,and the Device A's location phone number, which are received by Device B(S8).

Paragraph [0213]—This Paragraph [0213] illustrate(s) Device B's LocationOne Time Recording Software 20686c8A (Paragraph [0195]) of Device A andDevice B's Location One Time Recording Software 20686c1B (Paragraph[0205]) of Device B, which store the current location of Device B forone time. In the present embodiment, the user of Device B inputs aDevice B's location one time recording signal (S1). Here, the Device B'slocation one time recording signal is a signal which instructs CPU 211(FIG. 1) of Device B to initiate implementing the following steps. CPU211 (FIG. 1) of Device B identifies the current time and stores the datain column ‘Time Data’ (e.g., Time Data#5) of Device B's Location DataStorage Area 20686b1B (Paragraph [0200]) (S2). CPU 211 of Device Bidentifies the current geographic location data of Device B and storesthe data in column ‘Device B's Location Data’ (e.g., Device B's LocationData#5) of Device B's Location Data Storage Area 20686b1B (Paragraph[0200]) (S3). CPU 211 of Device B retrieves the time data and the DeviceB's location data from Device B's Location Data Storage Area 20686b1B(Paragraph [0200]) and sends the data to Device A via Antenna 218(FIG. 1) (S4). CPU 211 of Device A receives the time data and the DeviceB's location data from Device B and stores the data in Device B'sLocation Data Storage Area 20686b2A (Paragraph [0191]) (S5).

Paragraph [0214]—This Paragraph [0214] illustrate(s) Device B's LocationContinuous Recording Software 20686c9A (Paragraph [0195]) of Device Aand Device B's Location Continuous Recording Software 20686c2B(Paragraph [0205]) of Device B, which continuously store the currentlocation of Device B. In the present embodiment, the user of Device Binputs a Device B's location continuous recording signal (S1). Here, theDevice B's location continuous recording signal is a signal whichinstructs CPU 211 (FIG. 1) of Device B to initiate implementing thefollowing steps. CPU 211 (FIG. 1) of Device B identifies the currenttime and adds the data as a new time data in column ‘Time Data’ (e.g.,Time Data#5) of Device B's Location Data Storage Area 20686b1B(Paragraph [0200]) (S2). CPU 211 of Device B identifies the currentgeographic location data of Device B and adds the data as a new DeviceB's location data in column ‘Device B's Location Data’ (e.g., Device B'sLocation Data#5) of Device B's Location Data Storage Area 20686b1B(Paragraph [0200]) (S3). CPU 211 of Device B retrieves the new time dataand Device B's location data from Device B's Location Data Storage Area20686b1B (Paragraph [0200]) and sends the data to Device A via Antenna218 (FIG. 1) (S4). The sequence of S2 through S4 is repeatedPeriodically (S5).

Paragraph [0215]—This Paragraph [0215] illustrate(s) Device B's LocationDisplaying Software 20686c10A (Paragraph [0195]) of Device A, whichdisplays the current location of Device B on LCD 201 (FIG. 1) of DeviceA. In the present embodiment, CPU 211 (FIG. 1) of Device A retrieves alltime data from Device B's Location Data Storage Area 20686b2A (Paragraph[0191]) and displays a list of time data on LCD 201 (FIG. 1) of Device A(S1). The user of Device A selects a time data (e.g., Time Data#5) byutilizing Input Device 210 (FIG. 1) or via voice recognition system(S2). CPU 211 of Device A retrieves the corresponding Device B'slocation data (e.g., Device B's Location Data#5) (S3). CPU 211 of DeviceA retrieves the 3D map data from 3D Map Data Storage Area 20686b3A anddisplays the data on LCD 201 (FIG. 1) of Device A (S4). CPU 211 ofDevice A retrieves Icon Image Data#2 from Icon Image Data Storage Area20686b6A (Paragraph [0194]) (S5). CPU 211 of Device A displays the dataon LCD 201 of Device A at the location corresponding to the Device B'sLocation Data (e.g., Device B's Location Data#5) retrieved in S3 (S6).

Paragraph [0216]—This Paragraph [0216] illustrate(s) Device B's LocationReplaying Software 20686c11A (Paragraph [0195]) of Device A, whichreplays the location of Device B. In the present embodiment, CPU 211(FIG. 1) of Device A retrieves the 3D map data from 3D Map Data StorageArea 20686b3A and displays the data on LCD 201 (FIG. 1) of Device A(S1). CPU 211 of Device A retrieves the 1st time data (e.g., TimeData#5) stored in Device B's Location Data Storage Area 20686b2A(Paragraph [0191]) (S2). CPU 211 of Device A retrieves the correspondingDevice B's location data (e.g., Device B's Location Data#5) (S3). CPU211 of Device A retrieves Icon Image Data#2 from Icon Image Data StorageArea 20686b6A (Paragraph [0194]) (S4). CPU 211 of Device A displays thedate on LCD 201 of Device A at the location corresponding to the DeviceB's location data (e.g., Device B's Location Data#5) retrieved in S3(S5). The sequence of S2 through S5 is repeated with the 2nd time data(e.g., Time Data#6), the 3rd time data (e.g., Time Data#7), and the 4thtime data (e.g., Time Data#8) (S6).

Paragraph [0217]—This Paragraph [0217] illustrate(s) Device B's LocationStreet Address Displaying Software 20686c12A (Paragraph [0195]) ofDevice A, which displays the street address of the premises (e.g., ahotel or restaurant) where Device B is currently located. In the presentembodiment, CPU 211 (FIG. 1) of Device A retrieves all time data fromDevice B's Location Data Storage Area 20686b2A (Paragraph [0191]) anddisplays a list of time data on LCD 201 (FIG. 1) of Device A (S1). Theuser of Device A selects a time data (e.g., Time Data#5) by utilizingInput Device 210 (FIG. 1) or via voice recognition system (S2). CPU 211of Device A retrieves the corresponding Device B's location data (e.g.,Device B's Location Data#5) (S3). CPU 211 of Device A identifies theclosest street address location data (e.g., Street Address LocationData#5) stored in Street Address Location Storage Area 20686b4A(Paragraph [0192]) (S4). CPU 211 of Device A retrieves the correspondingstreet address data (e.g., Street Address Data#5) from Street AddressLocation Storage Area 20686b4A (Paragraph [0192]) and displays the dataon LCD 201 (FIG. 1) of Device A (S5).

Paragraph [0218]—This Paragraph [0218] illustrate(s) Device B's LocationPhone Number Displaying Software 20686c13A (Paragraph [0195]) of DeviceA, which displays the phone number of the premises (e.g., a hotel orrestaurant) where Device B is currently located. In the presentembodiment, CPU 211 (FIG. 1) of Device A retrieves all time data fromDevice B's Location Data Storage Area 20686b2A (Paragraph [0191]) anddisplays a list of time data on LCD 201 (FIG. 1) of Device A (S1). Theuser of Device A selects a time data (e.g., Time Data#5) by utilizingInput Device 210 (FIG. 1) or via voice recognition system (S2). CPU 211of Device A retrieves the corresponding Device B's location data (e.g.,Device B's Location Data#5) (S3). CPU 211 of Device A identifies theclosest phone number location data (e.g., Phone Number Location Data#5)stored in Phone Number Location Storage Area 20686b5A (Paragraph [0193])(S4). CPU 211 of Device A retrieves the corresponding phone number data(e.g., Phone Number Data#5) from Phone Number Location Storage Area20686b5A (Paragraph [0193]) and displays the data on LCD 201 (FIG. 1) ofDevice A (S5).

Paragraph [0219]—This Paragraph [0219] illustrate(s) Device B's LocationInformation Sending/Receiving Software 20686c14A (Paragraph [0195]) ofDevice A and Device B's Location Information Sending Software 20686c7B(Paragraph [0205]) of Device B, which send the Device B's location data,the Device B's location street address, and the Device B's locationphone number to Device A. In the present embodiment, CPU 211 (FIG. 1) ofDevice B retrieves all time data from Device B's Location Data StorageArea 20686b2B and displays a list of time data on LCD 201 (FIG. 1) ofDevice B (S1). The user of Device B selects a time data (e.g., TimeData#5) by utilizing Input Device 210 (FIG. 1) or via voice recognitionsystem (S2). CPU 211 of Device B retrieves the corresponding Device B'slocation data (e.g., Device B's Location Data#5) (S3). CPU 211 of DeviceB identifies the closest street address location data (e.g., StreetAddress Location Data#5) stored in Street Address Location Storage Area20686b4B (Paragraph [0202]) (S4). CPU 211 of Device B retrieves thecorresponding street address data (e.g., Street Address Data#5) fromStreet Address Location Storage Area 20686b4B (Paragraph [0202]) anddisplays the data on LCD 201 (FIG. 1) of Device B (S5). CPU 211 ofDevice B identifies the closest phone number location data (e.g., PhoneNumber Location Data#5) stored in Phone Number Location Storage Area20686b5B (Paragraph [0203]) (S6). CPU 211 of Device B retrieves thecorresponding phone number data (e.g., Phone Number Data#5) from PhoneNumber Location Storage Area 20686b5B (Paragraph [0203]) and displaysthe data on LCD 201 (FIG. 1) of Device B (S7). CPU 211 of Device B sendsthe Device B's location data, the Device B's location street address,and the Device B's location phone number, which are received by Device A(S8).

Paragraph [0220]—<<CCD Dictionary Function>>

Paragraph [0221]—Paragraph [0222] through Paragraph [0241] illustrate(s)the CCD dictionary function which enables the user of CommunicationDevice 200 to utilize Communication Device 200 as a language dictionary.

Paragraph [0222]—This Paragraph [0222] illustrate(s) the storage areaincluded in Host H (Paragraph [0022]). In the present embodiment, Host Hincludes CCD Dictionary Information Storage Area H87a of which the dataand the software programs stored therein are described in Paragraph[0223].

Paragraph [0223]—This Paragraph [0223] illustrate(s) the storage areasincluded in CCD Dictionary Information Storage Area H87a (Paragraph[0222]). In the present embodiment, CCD Dictionary Information StorageArea H87a includes CCD Dictionary Data Storage Area H87b and CCDDictionary Software Storage Area H87c. CCD Dictionary Data Storage AreaH87b stores the data necessary to implement the present function on theside of Host H (Paragraph [0022]), such as the ones described inParagraph [0224] through Paragraph [0227]. CCD Dictionary SoftwareStorage Area H87c stores the software programs necessary to implementthe present function on the side of Host H, such as the ones describedin Paragraph [0228].

Paragraph [0224]—This Paragraph [0224] illustrate(s) the storage areasincluded in CCD Dictionary Data Storage Area H87b (Paragraph [0223]). Inthe present embodiment, CCD Dictionary Data Storage Area H87b includesDictionary Data Storage Area H87b1 and Work Area H87b2. Dictionary DataStorage Area H87b1 stores the data described in Paragraph [0225]. WorkArea H87b2 is utilized as a work area to perform calculation andtemporarily store data.

Paragraph [0225]—This Paragraph [0225] illustrate(s) the storage areasincluded in Dictionary Data Storage Area H87b1 (Paragraph [0224]). Inthe present embodiment, Dictionary Data Storage Area H87b1 includesEnglish/English Dictionary Data Storage Area H87b1a and English/JapaneseDictionary Data Storage Area H87b1b. English/English Dictionary DataStorage Area H87b1a stores the data described in Paragraph [0226].English/Japanese Dictionary Data Storage Area H87b1b stores the datadescribed in Paragraph [0227].

Paragraph [0226]—This Paragraph [0226] illustrate(s) the data stored inEnglish/English Dictionary Data Storage Area H87b1a (Paragraph [0225]).In the present embodiment, English/English Dictionary Data Storage AreaH87b1a comprises two columns, i.e., ‘English Term’ and ‘EnglishExplanation Data’. Column ‘English Term’ stores the English terms, andeach English term represents an English word. Each English term includesalphanumeric data. Column ‘English Explanation Data’ stores the Englishexplanation data, and each English explanation data represents theexplanation in English of the corresponding English term. Each Englishexplanation data includes alphanumeric data. In the present embodiment,English/English Dictionary Data Storage Area H87b1a stores the followingdata: the English term ‘English Term#1’ and the corresponding Englishexplanation data ‘English Explanation Data#1’; the English term ‘EnglishTerm#2’ and the corresponding English explanation data ‘EnglishExplanation Data#2’; the English term ‘English Term#3’ and thecorresponding English explanation data ‘English Explanation Data#3’; andthe English term ‘English Term#4’ and the corresponding Englishexplanation data ‘English Explanation Data#4’.

Paragraph [0227]—This Paragraph [0227] illustrate(s) the data stored inEnglish/Japanese Dictionary Data Storage Area H87b1b (Paragraph [0225]).In the present embodiment, English/Japanese Dictionary Data Storage AreaH87b1b comprises two columns, i.e., ‘English Term’ and ‘JapaneseExplanation Data’. Column ‘English Term’ stores the English terms, andeach English term represents an English word. Each English term includesalphanumeric data. The English terms stored in English/JapaneseDictionary Data Storage Area H87b1b (Paragraph [0227]) are identical tothe ones stored in English/English Dictionary Data Storage Area H87b1a(Paragraph [0226]). Column ‘Japanese Explanation Data’ stores theJapanese explanation data, and each Japanese explanation data representsthe explanation in Japanese of the corresponding English term. EachJapanese explanation data includes alphanumeric data. In the presentembodiment, English/Japanese Dictionary Data Storage Area H87b1b storesthe following data: the English term ‘English Term#1’ and thecorresponding Japanese explanation data ‘Japanese Explanation Data#1’;the English term ‘English Term#2’ and the corresponding Japaneseexplanation data ‘Japanese Explanation Data#2’; the English term‘English Term#3’ and the corresponding Japanese explanation data‘Japanese Explanation Data#3; and the English term ‘English Term#4’ andthe corresponding Japanese explanation data Japanese ExplanationData#4’.

Paragraph [0228]—This Paragraph [0228] illustrate(s) the softwareprograms stored in CCD Dictionary Software Storage Area H87c (Paragraph[0223]). In the present embodiment, CCD Dictionary Software Storage AreaH87c stores Dictionary Data Downloading Software H87c1 and ExplanationData Retrieving Software H87c2. Dictionary Data Downloading SoftwareH87c1 is the software program described in Paragraph [0237]. ExplanationData Retrieving Software H87c2 is the software program described inParagraph [0238]. Paragraph [0229]—This Paragraph [0229] illustrate(s)the storage area included in RAM 206 (FIG. 1) of Communication Device200. In the present embodiment, RAM 206 includes CCD DictionaryInformation Storage Area 20687a of which the data and the softwareprograms stored therein are described in Paragraph [0231].

Paragraph [0230]—The data and/or the software programs stored in CCDDictionary Information Storage Area 20687a (Paragraph [0229]) may bedownloaded from Host H (Paragraph [0022]) in the manner described inParagraph [0416] through Paragraph [0422]. Paragraph [0231]—ThisParagraph [0231] illustrate(s) the storage areas included in CCDDictionary Information Storage Area 20687a (Paragraph [0229]). In thepresent embodiment, CCD Dictionary Information Storage Area 20687aincludes CCD Dictionary Data Storage Area 20687b and CCD DictionarySoftware Storage Area 20687c. CCD Dictionary Data Storage Area 20687bstores the data necessary to implement the present function on the sideof Communication Device 200, such as the ones described in Paragraph[0232] through Paragraph [0235]. CCD Dictionary Software Storage Area20687c stores the software programs necessary to implement the presentfunction on the side of Communication Device 200, such as the onesdescribed in Paragraph [0236].

Paragraph [0232]—This Paragraph [0232] illustrate(s) the storage areasincluded in CCD Dictionary Data Storage Area 20687b (Paragraph [0231]).In the present embodiment, CCD Dictionary Data Storage Area 20687bincludes Dictionary Data Storage Area 20687b1 and Work Area 20687b2.Dictionary Data Storage Area 20687b1 stores the data described inParagraph [0233]. Work Area 20687b2 is utilized as a work area toperform calculation and temporarily store data.

Paragraph [0233]—This Paragraph [0233] illustrate(s) the storage areasincluded in Dictionary Data Storage Area 20687b1 (Paragraph [0232]). Inthe present embodiment, Dictionary Data Storage Area 20687b1 includesEnglish/English Dictionary Data Storage Area 20687b1a andEnglish/Japanese Dictionary Data Storage Area 20687b1b. English/EnglishDictionary Data Storage Area 20687b1a stores the data described inParagraph [0234]. English/Japanese Dictionary Data Storage Area 20687b1bstores the data described in Paragraph [0235].

Paragraph [0234]—This Paragraph [0234] illustrate(s) the data stored inEnglish/English Dictionary Data Storage Area 20687b1a (Paragraph[0233]). In the present embodiment, English/English Dictionary DataStorage Area 20687b1a comprises two columns, i.e., ‘English Term’ and‘English Explanation Data’. Column ‘English Term’ stores the Englishterms, and each English term represents an English word. Each Englishterm includes alphanumeric data. Column ‘English Explanation Data’stores the English explanation data, and each English explanation datarepresents the explanation in English of the corresponding English term.Each English explanation data includes alphanumeric data. In the presentembodiment, English/English Dictionary Data Storage Area 20687b1a storesthe following data: the English term ‘English Term#1’ and thecorresponding English explanation data ‘English Explanation Data#1’; theEnglish term ‘English Term#2’ and the corresponding English explanationdata ‘English Explanation Data#2’; the English term ‘English Term#3’ andthe corresponding English explanation data ‘English Explanation Data#3’;and the English term ‘English Term#4’ and the corresponding Englishexplanation data ‘English Explanation Data#4’.

Paragraph [0235]—This Paragraph [0235] illustrate(s) the data stored inEnglish/Japanese Dictionary Data Storage Area 20687b1b (Paragraph[0233]). In the present embodiment, English/Japanese Dictionary DataStorage Area 20687b1b comprises two columns, i.e., ‘English Term’ and‘Japanese Explanation Data’. Column ‘English Term’ stores the Englishterms, and each English term represents an English word. Each Englishterm includes alphanumeric data. The English terms stored inEnglish/Japanese Dictionary Data Storage Area 20687b1b (Paragraph[0235]) are identical to the ones stored in English/English DictionaryData Storage Area 20687b1a (Paragraph [0234]). Column ‘JapaneseExplanation Data’ stores the Japanese explanation data, and eachJapanese explanation data represents the explanation in Japanese of thecorresponding English term. Each Japanese explanation data includesalphanumeric data. In the present embodiment, English/JapaneseDictionary Data Storage Area 20687b1b stores the following data: theEnglish term ‘English Term#1’ and the corresponding Japanese explanationdata ‘Japanese Explanation Data#1’; the English term ‘English Term#2’and the corresponding Japanese explanation data ‘Japanese ExplanationData#2; the English term ‘English Term#3’ and the corresponding Japaneseexplanation data ‘Japanese Explanation Data#3’; and the English term‘English Term#4’ and the corresponding Japanese explanation dataJapanese Explanation Data#4’.

Paragraph [0236]—This Paragraph [0236] illustrate(s) the softwareprograms stored in CCD Dictionary Software Storage Area 20687c(Paragraph [0231]). In the present embodiment, CCD Dictionary SoftwareStorage Area 20687c stores Dictionary Data Downloading Software 20687c1,Explanation Data Retrieving Software 20687c2, and CCD DictionarySoftware 20687c3. Dictionary Data Downloading Software 20687c1 is thesoftware program described in Paragraph [0237]. Explanation DataRetrieving Software 20687c2 is the software program described inParagraph [0238], Paragraph [0240]. CCD Dictionary Software 20687c3 isthe software program described in Paragraph [0239], and Paragraph[0241].

Paragraph [0237]—This Paragraph [0237] illustrate(s) Dictionary DataDownloading Software H87c1 (Paragraph [0228]) of Host H (Paragraph[0022]) and Dictionary Data Downloading Software 20687c1 (Paragraph[0236]) of Communication Device 200, which download the data stored inDictionary Data Storage Area H87b1 (Paragraph [0225]). In the presentembodiment, CPU 211 (FIG. 1) of Communication Device 200 sends, in awireless fashion via Antenna 218 (FIG. 1), a dictionary data downloadingrequest, which is received by Host H (S1). Here, the dictionary datadownloading request is a request to download the data stored inDictionary Data Storage Area H87b1 (Paragraph [0225]) of Host H. Inresponse, Host H retrieves all data from Dictionary Data Storage AreaH87b1 (Paragraph [0225]) and sends the data to Communication Device 200(S2). CPU 211 receives the data and stores them in Dictionary DataStorage Area 20687b1 (Paragraph [0233]) (S3).

Paragraph [0238]—This Paragraph [0238] illustrate(s) Explanation DataRetrieving Software 20687c2 (Paragraph [0236]) of Communication Device200, which displays on LCD 201 (FIG. 1) the explanations of the Englishterm input by utilizing Input Device 210 (FIG. 1) or via voicerecognition system. In the present embodiment, the user of CommunicationDevice 200 inputs an English term (e.g., English Term#1) by utilizingInput Device 210 (FIG. 1) or via voice recognition system (S1). CPU 211(FIG. 1) of Communication Device 200 searches English/English DictionaryData Storage Area 20687b1a (Paragraph [0234]) for the matching term(S2). CPU 211 then searches English/Japanese Dictionary Data StorageArea 20687b1b (Paragraph [0235]) for the matching term (S3). CPU 211stores the corresponding English explanation data (e.g., EnglishExplanation Data#1) in Work Area 20687b2 (Paragraph [0232]) (S4). CPU211 stores the corresponding Japanese explanation data (e.g., JapaneseExplanation Data#1) in Work Area 20687b2 (Paragraph [0232]) (S5). CPU211 retrieves the corresponding English explanation data (e.g., EnglishExplanation Data#1) and the corresponding Japanese explanation data(e.g., Japanese Explanation Data#1) from Work Area 20687b2 (Paragraph[0232]) and displays both data on LCD 201 (FIG. 1) (S6).

Paragraph [0239]—This Paragraph [0239] illustrate(s) CCD DictionarySoftware 20687c3 (Paragraph [0236]) of Communication Device 200, whichdisplays on LCD 201 (FIG. 1) the explanations of the English term inputvia CCD Unit 214 (FIG. 1). In the present embodiment, CPU 211 (FIG. 1)of Communication Device 200 inputs an image data from CCD Unit 214(FIG. 1) (S1). CPU 211 stores the image data input In S1 in Work Area20687b2 (Paragraph [0232]) (S2), and converts the image data to textdata and retrieves an English term (e.g., English Term#1) therefrom(S3). CPU 211 searches English/English Dictionary Data Storage Area20687b1a (Paragraph [0234]) for the matching term (S4). CPU 211 thensearches English/Japanese Dictionary Data Storage Area 20687b1b(Paragraph [0235]) for the matching term (S5). CPU 211 stores thecorresponding English explanation data (e.g., English ExplanationData#1) in Work Area 20687b2 (Paragraph [0232]) (S6). CPU 211 stores thecorresponding Japanese explanation data (e.g., Japanese ExplanationData#1) in Work Area 20687b2 (Paragraph [0232]) (S7). CPU 211 retrievesthe corresponding English explanation data and the correspondingJapanese explanation data from Work Area 20687b2 (Paragraph [0232]) anddisplays both data on LCD 201 (FIG. 1) (S8).

Paragraph [0240]—This Paragraph [0240] illustrate(s) Explanation DataRetrieving Software H87c2 (Paragraph [0228]) of Host H (Paragraph[0022]) and Explanation Data Retrieving Software 20687c2 (Paragraph[0236]) of Communication Device 200, which display on LCD 201 (FIG. 1)the explanations of the English term input by utilizing Input Device 210(FIG. 1) or via voice recognition system. The explanation data areretrieved from Host H (Paragraph [0022]) in this embodiment. Referringto the present embodiment, the user of Communication Device 200 inputsan English term (e.g., English Term#1) by utilizing Input Device 210(FIG. 1) or via voice recognition system (S1). CPU 211 (FIG. 1) ofCommunication Device 200 sends, in a wireless fashion via Antenna 218(FIG. 1), the English term (e.g., English Term#1) input In S1, which isreceived by Host H (S2). Host H searches English/English Dictionary DataStorage Area H87b1a (Paragraph [0226]) for the matching term (S3). HostH searches English/Japanese Dictionary Data Storage Area H87b1b(Paragraph [0227]) for the matching term (S4). Host H sends thecorresponding English explanation data (e.g., English ExplanationData#1) and the corresponding Japanese explanation data (e.g., JapaneseExplanation Data#1), which are received by Communication Device 200(S5). CPU 211 of Communication Device 200 stores the correspondingEnglish explanation data (e.g., English Explanation Data#1) in Work Area20687b2 (Paragraph [0232]) (S6). CPU 211 stores the correspondingJapanese explanation data (e.g., Japanese Explanation Data#1) in WorkArea 20687b2 (Paragraph [0232]) (S7). CPU 211 retrieves thecorresponding English explanation data and the corresponding Japaneseexplanation data from Work Area 20687b2 (Paragraph [0232]) and displaysboth data on LCD 201 (FIG. 1) (S8).

Paragraph [0241]—This Paragraph [0241] illustrate(s) Explanation DataRetrieving Software H87c2 (Paragraph [0228]) of Host H (Paragraph[0022]) and CCD Dictionary Software 20687c3 (Paragraph [0236]) ofCommunication Device 200, which display on LCD 201 (FIG. 1) theexplanations of the English term input via CCD Unit 214 (FIG. 1). Theexplanation data are retrieved from Host H (Paragraph [0022]) in thisembodiment. In the present embodiment, CPU 211 (FIG. 1) of CommunicationDevice 200 inputs an image data from CCD Unit 214 (FIG. 1) (S1). CPU 211stores the image data input In S1 in Work Area 20687b2 (Paragraph[0232]) (S2), and converts the image data to text data and retrieves anEnglish term (e.g., English Term#1) therefrom (S3). CPU 211 sends, in awireless fashion via Antenna 218 (FIG. 1), the English term (e.g.,English Term#1) input In S1, which is received by Host H (S4). Host Hsearches English/English Dictionary Data Storage Area H87b1a (Paragraph[0226]) for the matching term (S5). Host H searches English/JapaneseDictionary Data Storage Area H87b1b (Paragraph [0227]) for the matchingterm (S6). Host H sends the corresponding English explanation data(e.g., English Explanation Data#1) and the corresponding Japaneseexplanation data (e.g., Japanese Explanation Data#1), which are receivedby Communication Device 200 (S7). CPU 211 of Communication Device 200stores the corresponding English explanation data (e.g., EnglishExplanation Data#1) in Work Area 20687b2 (Paragraph [0232]) (S8). CPU211 stores the corresponding Japanese explanation data (e.g., JapaneseExplanation Data#1) in Work Area 20687b2 (Paragraph [0232]) (S9). CPU211 retrieves the corresponding English explanation data and thecorresponding Japanese explanation data from Work Area 20687b2(Paragraph [0232]) and displays both data on LCD 201 (FIG. 1) (S10).

Paragraph [0242]—<<Multiple Type TV Program Distributing System>>

Paragraph [0243]—This Paragraph [0243] illustrate(s) the connectionsbetween Host H (Paragraph [0022]) and the three broadcast centers, i.e.,Satellite TV Broadcast Center 94TVBC1 (Paragraph [0243]), Ground Wave TVBroadcast Center 94TVBC2 (Paragraph [0243]), and Cable TV BroadcastCenter 94TVBC3 (Paragraph [0243]). Satellite TV Broadcast Center 94TVBC1(Paragraph [0243]) is the broadcast center which broadcasts thesatellite TV program data. Here, the satellite TV program data is thedata distributed from Satellite TV Broadcast Center 94TVBC1 (Paragraph[0243]) which is designed to be output from displays, such as TVmonitors. Ground Wave TV Broadcast Center 94TVBC2 (Paragraph [0243]) isthe broadcast center which broadcasts the ground wave TV program data.Here, the ground wave TV program data is the data distributed fromGround Wave TV Broadcast Center 94TVBC2 (Paragraph [0243]) which isdesigned to be output from displays, such as TV monitors. Cable TVBroadcast Center 94TVBC3 (Paragraph [0243]) is the broadcast centerwhich broadcasts the cable TV program data. Here, the cable TV programdata is the data distributed from Cable TV Broadcast Center 94TVBC3(Paragraph [0243]) which is designed to be output from displays, such asTV monitors. The foregoing three broadcast centers broadcast the TVprogram data in their ordinary manner, and also distribute the same TVprogram data to Host H via Network NT (e.g., the Internet) in order forCommunication Device 200 to display the TV program data by implementingthe present system. Host H receives the TV program data from theforegoing three broadcast centers realtime, twenty-four hour a day andseven days a week of which the details are described hereinafter.

Paragraph [0244]—This Paragraph [0244] illustrate(s) another embodimentof the connection between Host H (Paragraph [0022]) and Satellite TVBroadcast Center 94TVBC1 (Paragraph [0243]). Satellite TV BroadcastCenter 94TVBC1 (Paragraph [0243]) is the broadcast center whichbroadcasts the satellite TV program data. Here, the satellite TV programdata is the data distributed from Satellite TV Broadcast Center 94TVBC1(Paragraph [0243]) which is designed to be output from displays, such asTV monitors. Satellite TV Broadcast Center 94TVBC1 (Paragraph [0243])broadcasts the satellite TV program data in their ordinary manner viaArtificial Satellite AS94, which is received by Host H in order forCommunication Device 200 to display the satellite TV program data byimplementing the present system.

Paragraph [0245]—This Paragraph [0245] illustrate(s) another embodimentof the connection between Host H (Paragraph [0022]) and Ground Wave TVBroadcast Center 94TVBC2 (Paragraph [0243]). Ground Wave TV BroadcastCenter 94TVBC2 (Paragraph [0243]) is the broadcast center whichbroadcasts the ground wave TV program data. Here, the ground wave TVprogram data is the data distributed from Ground Wave TV BroadcastCenter 94TVBC2 (Paragraph [0243]) which is designed to be output fromdisplays, such as TV monitors. Ground Wave TV Broadcast Center 94TVBC2(Paragraph [0243]) broadcasts the ground wave TV program data in theirordinary manner via Antenna Ant94, which is received by Host H in orderfor Communication Device 200 to display the ground wave TV program databy implementing the present system and/or the cellular TV function.

Paragraph [0246]—This Paragraph [0246] illustrate(s) another embodimentof the connection between Host H (Paragraph [0022]) and Cable TVBroadcast Center 94TVBC3 (Paragraph [0243]). Cable TV Broadcast Center94TVBC3 (Paragraph [0243]) is the broadcast center which broadcasts thecable TV program data. Here, the cable TV program data is the datadistributed from Cable TV Broadcast Center 94TVBC3 (Paragraph [0243])which is designed to be output from displays, such as TV monitors. CableTV Broadcast Center 94TVBC3 (Paragraph [0243]) broadcasts the cable TVprogram data in their ordinary manner via Cable Cbl94, which is receivedby Host H in order for Communication Device 200 to display the cable TVprogram data by implementing the present system and/or the cellular TVfunction.

Paragraph [0247]—This Paragraph [0247] illustrate(s) the storage areaincluded in Host H (Paragraph [0022]). In the present embodiment, Host Hincludes Multiple Type TV Program Information Storage Area H94a of whichthe data and the software programs stored therein are described inParagraph [0248].

Paragraph [0248]—This Paragraph [0248] illustrate(s) the storage areasincluded in Multiple Type TV Program Information Storage Area H94a(Paragraph [0247]). In the present embodiment, Multiple Type TV ProgramInformation Storage Area H94a includes Multiple Type TV Program DataStorage Area H94b and Multiple Type TV Program Data Software StorageArea H94c. Multiple Type TV Program Data Storage Area H94b stores thedata necessary to implement the present function on the side of Host H(Paragraph [0022]), such as the ones described in Paragraph [0249]through Paragraph [0252]. Multiple Type TV Program Data Software StorageArea H94c stores the software programs necessary to implement thepresent function on the side of Host H, such as the ones described inParagraph [0253].

Paragraph [0249]—This Paragraph [0249] illustrate(s) the storage areasincluded in Multiple Type TV Program Data Storage Area H94b (Paragraph[0248]). In the present embodiment, Multiple Type TV Program DataStorage Area H94b includes Satellite TV Program Data Storage Area H94b1,Ground Wave TV Program Data Storage Area H94b2, Cable TV Program DataStorage Area H94b3, and Work Area H94b4. Satellite TV Program DataStorage Area H94b1 stores the data described in Paragraph [0250]. GroundWave TV Program Data Storage Area H94b2 stores the data described inParagraph [0251]. Cable TV Program Data Storage Area H94b3 stores thedata described in Paragraph [0252]. Work Area H94b4 is utilized as awork area to perform calculation and temporarily store data.

Paragraph [0250]—This Paragraph [0250] illustrate(s) the data stored inSatellite TV Program Data Storage Area H94b1 (Paragraph [0248]). In thepresent embodiment, Satellite TV Program Data Storage Area H94b1comprises two columns, i.e., ‘Satellite TV Program ID’ and ‘Satellite TVProgram Data’. Column ‘Satellite TV Program ID’ stores the satellite TVprogram IDs, and each satellite TV program ID is an identification ofthe corresponding satellite TV program data stored in column ‘SatelliteTV Program Data’. Column ‘Satellite TV Program Data’ stores thesatellite TV program data, and each satellite TV program data is thedata received from Satellite TV Broadcast Center 94TVBC1 (Paragraph[0243]). In the present embodiment, Satellite TV Program Data StorageArea H94b1 stores the following data: the satellite TV program ID‘Satellite TV Program#1’ and the corresponding satellite TV program data‘Satellite TV Program Data#1’; the satellite TV program ID ‘Satellite TVProgram#2’ and the corresponding satellite TV program data ‘Satellite TVProgram Data#2’; the satellite TV program ID ‘Satellite TV Program#3’and the corresponding satellite TV program data ‘Satellite TV ProgramData#3’; and the satellite TV program ID ‘Satellite TV Program#4’ andthe corresponding satellite TV program data ‘Satellite TV ProgramData#4’.

Paragraph [0251]—This Paragraph [0251] illustrate(s) the data stored inGround Wave TV Program Data Storage Area H94b2 (Paragraph [0248]). Inthe present embodiment, Ground Wave TV Program Data Storage Area H94b2comprises two columns, i.e., ‘Ground Wave TV Program ID’ and ‘GroundWave TV Program Data’. Column ‘Ground Wave TV Program ID’ stores theground wave TV program IDs, and each ground wave TV program ID is anidentification of the corresponding ground wave TV program data storedin column ‘Satellite TV Program Data’. Column ‘Ground Wave TV ProgramData’ stores the ground wave TV program data, and each ground wave TVprogram data is the data received from Ground Wave TV Broadcast Center94TVBC2 (Paragraph [0243]). In the present embodiment, Ground Wave TVProgram Data Storage Area H94b2 stores the following data: the groundwave TV program ID ‘Ground Wave TV Program#1’ and the correspondingground wave TV program data ‘Ground Wave TV Program Data#1’; the groundwave TV program ID ‘Ground Wave TV Program#2’ and the correspondingground wave TV program data ‘Ground Wave TV Program Data#2’; the groundwave TV program ID ‘Ground Wave TV Program#3’ and the correspondingground wave TV program data ‘Ground Wave TV Program Data#3’; and theground wave TV program ID ‘Ground Wave TV Program#4’ and thecorresponding ground wave TV program data ‘Ground Wave TV ProgramData#4’.

Paragraph [0252]—This Paragraph [0252] illustrate(s) the data stored inCable TV Program Data Storage Area H94b3 (Paragraph [0248]). In thepresent embodiment, Cable TV Program Data Storage Area H94b3 comprisestwo columns, i.e., ‘Cable TV Program ID’ and ‘Cable TV Program Data’.Column ‘Cable TV Program ID’ stores the cable TV program IDs, and eachcable TV program ID is an identification of the corresponding cable TVprogram data stored in column ‘Satellite TV Program Data’. Column ‘CableTV Program Data’ stores the cable TV program data, and each cable TVprogram data is the data received from Cable TV Broadcast Center 94TVBC3(Paragraph [0243]). In the present embodiment, Cable TV Program DataStorage Area H94b3 stores the following data: the cable TV program ID‘Cable TV Program#1’ and the corresponding cable TV program data ‘CableTV Program Data#1’; the cable TV program ID ‘Cable TV Program#2’ and thecorresponding cable TV program data ‘Cable TV Program Data#2’; the cableTV program ID ‘Cable TV Program#3’ and the corresponding cable TVprogram data ‘Cable TV Program Data#3’; and the cable TV program ID‘Cable TV Program#4’ and the corresponding cable TV program data ‘CableTV Program Data#4’.

Paragraph [0253]—This Paragraph [0253] illustrate(s) the softwareprograms stored in Multiple Type TV Program Data Software Storage AreaH94c (Paragraph [0248]). In the present embodiment, Multiple Type TVProgram Data Software Storage Area H94c stores Satellite TV Program DataReceiving Software H94c1, Ground Wave TV Program Data Receiving SoftwareH94c2, Cable TV Program Data Receiving Software H94c3, Satellite TVProgram Data Sending/Receiving Software H94c4, Ground Wave TV ProgramData Sending/Receiving Software H94c5, and Cable TV Program DataSending/Receiving Software H94c6. Satellite TV Program Data ReceivingSoftware H94c1 is the software program described in Paragraph [0262].Ground Wave TV Program Data Receiving Software H94c2 is the softwareprogram described in Paragraph [0263]. Cable TV Program Data ReceivingSoftware H94c3 is the software program described in Paragraph [0264].Satellite TV Program Data Sending/Receiving Software H94c4 is thesoftware program described in Paragraph [0265]. Ground Wave TV ProgramData Sending/Receiving Software H94c5 is the software program describedin Paragraph [0266]. Cable TV Program Data Sending/Receiving SoftwareH94c6 is the software program described in Paragraph [0267].

Paragraph [0254]—This Paragraph [0254] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Communication Device 200. In the presentembodiment, RAM 206 includes Multiple Type TV Program InformationStorage Area 20694a of which the data and the software programs storedtherein are described in Paragraph [0256].

Paragraph [0255]—The data and/or the software programs stored inMultiple Type TV Program Information Storage Area 20694a (Paragraph[0254]) may be downloaded from Host H (Paragraph [0022]) in the mannerdescribed in Paragraph [0416] through Paragraph [0422].

Paragraph [0256]—This Paragraph [0256] illustrate(s) the storage areasincluded in Multiple Type TV Program Information Storage Area 20694a(Paragraph [0254]). In the present embodiment, Multiple Type TV ProgramInformation Storage Area 20694a includes Multiple Type TV Program DataStorage Area 20694b and Multiple Type TV Program Data Software StorageArea 20694c. Multiple Type TV Program Data Storage Area 20694b storesthe data necessary to implement the present function on the side ofCommunication Device 200, such as the ones described in Paragraph [0257]through Paragraph [0260]. Multiple Type TV Program Data Software StorageArea 20694c stores the software programs necessary to implement thepresent function on the side of Communication Device 200, such as theones described in Paragraph [0261].

Paragraph [0257]—This Paragraph [0257] illustrate(s) the storage areasincluded in Multiple Type TV Program Data Storage Area 20694b (Paragraph[0256]). In the present embodiment, Multiple Type TV Program DataStorage Area 20694b includes Satellite TV Program Data Storage Area20694b1, Ground Wave TV Program Data Storage Area 20694b2, Cable TVProgram Data Storage Area 20694b3, and Work Area 20694b4. Satellite TVProgram Data Storage Area 20694b1 stores the data described in Paragraph[0258]. Ground Wave TV Program Data Storage Area 20694b2 stores the datadescribed in Paragraph [0259]. Cable TV Program Data Storage Area20694b3 stores the data described in Paragraph [0260]. Work Area 20694b4is utilized as a work area to perform calculation and temporarily storedata.

Paragraph [0258]—This Paragraph [0258] illustrate(s) the data stored inSatellite TV Program Data Storage Area 20694b1 (Paragraph [0257]). Inthe present embodiment, Satellite TV Program Data Storage Area 20694b1comprises two columns, i.e., ‘Satellite TV Program ID’ and ‘Satellite TVProgram Data’. Column ‘Satellite TV Program ID’ stores the satellite TVprogram IDs, and each satellite TV program ID is an identification ofthe corresponding satellite TV program data stored in column ‘SatelliteTV Program Data’. Column ‘Satellite TV Program Data’ stores thesatellite TV program data, and each satellite TV program data is thedata received from Host H. In the present embodiment, Satellite TVProgram Data Storage Area 20694b1 stores the following data: thesatellite TV program ID ‘Satellite TV Program#1’ and the correspondingsatellite TV program data ‘Satellite TV Program Data#1’; the satelliteTV program ID ‘Satellite TV Program#2’ and the corresponding satelliteTV program data ‘Satellite TV Program Data#2’; the satellite TV programID ‘Satellite TV Program#3’ and the corresponding satellite TV programdata ‘Satellite TV Program Data#3’; and the satellite TV program ID‘Satellite TV Program#4’ and the corresponding satellite TV program data‘Satellite TV Program Data#4’.

Paragraph [0259]—This Paragraph [0259] illustrate(s) the data stored inGround Wave TV Program Data Storage Area 20694b2 (Paragraph [0257]). Inthe present embodiment, Ground Wave TV Program Data Storage Area 20694b2comprises two columns, i.e., ‘Ground Wave TV Program ID’ and ‘GroundWave TV Program Data’. Column ‘Ground Wave TV Program ID’ stores theground wave TV program IDs, and each ground wave TV program ID is anidentification of the corresponding ground wave TV program data storedin column ‘Satellite TV Program Data’. Column ‘Ground Wave TV ProgramData’ stores the ground wave TV program data, and each ground wave TVprogram data is the data received from Host H. In the presentembodiment, Ground Wave TV Program Data Storage Area 20694b2 stores thefollowing data: the ground wave TV program ID ‘Ground Wave TV Program#1’and the corresponding ground wave TV program data ‘Ground Wave TVProgram Data#1’; the ground wave TV program ID ‘Ground Wave TVProgram#2’ and the corresponding ground wave TV program data ‘GroundWave TV Program Data#2’; the ground wave TV program ID ‘Ground Wave TVProgram#3’ and the corresponding ground wave TV program data ‘GroundWave TV Program Data#3’; and the ground wave TV program ID ‘Ground WaveTV Program#4’ and the corresponding ground wave TV program data ‘GroundWave TV Program Data#4’.

Paragraph [0260]—This Paragraph [0260] illustrate(s) the data stored inCable TV Program Data Storage Area 20694b3 (Paragraph [0257]). In thepresent embodiment, Cable TV Program Data Storage Area 20694b3 comprisestwo columns, i.e., ‘Cable TV Program ID’ and ‘Cable TV Program Data’.Column ‘Cable TV Program ID’ stores the cable TV program IDs, and eachcable TV program ID is an identification of the corresponding cable TVprogram data stored in column ‘Satellite TV Program Data’. Column ‘CableTV Program Data’ stores the cable TV program data, and each cable TVprogram data is the data received from Host H. In the presentembodiment, Cable TV Program Data Storage Area 20694b3 stores thefollowing data: the cable TV program ID ‘Cable TV Program#1’ and thecorresponding cable TV program data ‘Cable TV Program Data#1’; the cableTV program ID ‘Cable TV Program#2’ and the corresponding cable TVprogram data ‘Cable TV Program Data#2’; the cable TV program ID ‘CableTV Program#3’ and the corresponding cable TV program data ‘Cable TVProgram Data#3’; and the cable TV program ID ‘Cable TV Program#4’ andthe corresponding cable TV program data ‘Cable TV Program Data#4’.

Paragraph [0261]—This Paragraph [0261] illustrate(s) the softwareprograms stored in Multiple Type TV Program Data Software Storage Area20694c (Paragraph [0256]). In the present embodiment, Multiple Type TVProgram. Data Software Storage Area 20694c stores Satellite TV ProgramData Sending/Receiving Software 20694c1, Ground Wave TV Program DataSending/Receiving Software 20694c2, and Cable TV Program DataSending/Receiving Software 20694c3. Satellite TV Program DataSending/Receiving Software 20694c1 is the software program described inParagraph [0262]. Ground Wave TV Program Data Sending/Receiving Software20694c2 is the software program described in Paragraph [0263]. Cable TVProgram Data Sending/Receiving Software 20694c3 is the software programdescribed in Paragraph [0264].

Paragraph [0262]—This Paragraph [0262] illustrate(s) Satellite TVProgram Data Receiving Software H94c1 (Paragraph [0253]) of Host H(Paragraph [0022]), which receives the satellite TV program data fromSatellite TV Broadcast Center 94TVBC1 (Paragraph [0243]). In the presentembodiment, Host H receives the satellite TV program data (e.g.,Satellite TV Program Data#1 Through #4) from Satellite TV BroadcastCenter 94TVBC1 (Paragraph [0243]) (S1). Host H stores the satellite TVprogram data (e.g., Satellite TV Program Data#1 Through #4) in SatelliteTV Program Data Storage Area H94b1 (Paragraph [0250]) (S2). Theforegoing sequence is repeated periodically.

Paragraph [0263]—This Paragraph [0263] illustrate(s) Ground Wave TVProgram Data Receiving Software H94c2 (Paragraph [0253]) of Host H(Paragraph [0022]), which receives the ground wave TV program data fromGround Wave TV Broadcast Center 94TVBC2 (Paragraph [0243]). In thepresent embodiment, Host H receives the ground wave TV program data(e.g., Ground Wave TV Program Data#1 Through #4) from Ground Wave TVBroadcast Center 94TVBC2 (Paragraph [0243]) (S1). Host H stores theground wave TV program data (e.g., Ground Wave TV Program Data#1 Through#4) in Ground Wave TV Program Data Storage Area H94b2 (Paragraph [0251])(S2). The foregoing sequence is repeated periodically.

Paragraph [0264]—This Paragraph [0264] illustrate(s) Cable TV ProgramData Receiving Software H94c3 (Paragraph [0253]) of Host H (Paragraph[0022]), which receives the cable TV program data from Cable TVBroadcast Center 94TVBC3 (Paragraph [0243]). In the present embodiment,Host H receives the cable TV program data (e.g., Cable TV Program Data#1Through #4) from Cable TV Broadcast Center 94TVBC3 (Paragraph [0243])(S1). Host H stores the cable TV program data (e.g., Cable TV ProgramData#1 Through #4) in Cable TV Program Data Storage Area H94b3(Paragraph [0252]) (S2). The foregoing sequence is repeatedperiodically.

Paragraph [0265]—This Paragraph [0265] illustrate(s) Satellite TVProgram Data Sending/Receiving Software H94c4 (Paragraph [0253]) of HostH (Paragraph [0022]) and Satellite TV Program Data Sending/ReceivingSoftware 20694c1 (Paragraph [0261]) of Communication Device 200, whichsends and receives the satellite TV program data. In the presentembodiment, Host H retrieves all satellite TV program data (e.g.,Satellite TV Program Data#1 Through #4) from Satellite TV Program DataStorage Area H94b1 (Paragraph [0250]) and sends the data toCommunication Device 200 (S1). CPU 211 (FIG. 1) of Communication Device200 receives the satellite TV program data (e.g., Satellite TV ProgramData#1 Through #4) from Host H via Antenna 218 (FIG. 1) (S2). CPU 211stores the satellite TV program data (e.g., Satellite TV Program Data#1Through #4) in Satellite TV Program Data Storage Area 20694b1 (Paragraph[0258]) (S3). The foregoing sequence is repeated periodically.

Paragraph [0266]—This Paragraph [0266] illustrate(s) Ground Wave TVProgram Data Sending/Receiving Software H94c5 (Paragraph [0253]) of HostH (Paragraph [0022]) and Ground Wave TV Program Data Sending/ReceivingSoftware 20694c2 (Paragraph [0261]) of Communication Device 200, whichsends and receives the ground wave TV program data. In the presentembodiment, Host H retrieves all ground wave TV program data (e.g.,Ground Wave TV Program Data#1 Through #4) from Ground Wave TV ProgramData Storage Area H94b2 (Paragraph [0251]) and sends the data toCommunication Device 200 (S1). CPU 211 (FIG. 1) of Communication Device200 receives the ground wave TV program data (e.g., Ground Wave TVProgram Data#1 Through #4) from Host H (Paragraph [0022]) (S2). CPU 211stores the ground wave TV program data (e.g., Ground Wave TV ProgramData#1 Through #4) in Ground Wave TV Program Data Storage Area 20694b2(Paragraph [0259]) (S3). The foregoing sequence is repeatedperiodically.

Paragraph [0267]—This Paragraph [0267] illustrate(s) Cable TV ProgramData Sending/Receiving Software H94c6 (Paragraph [0253]) of Host H(Paragraph [0022]) and Cable TV Program Data Sending/Receiving Software20694c3 (Paragraph [0261]) of Communication Device 200, which sends andreceives the cable TV program data. In the present embodiment, Host Hretrieves all cable TV program data (e.g., Cable TV Program Data#1Through #4) from Cable TV Program Data Storage Area H94b3 (Paragraph[0252]) and sends the data to Communication Device 200 (S1). CPU 211(FIG. 1) of Communication Device 200 receives the cable TV program data(e.g., Cable TV Program Data#1 Through #4) from Host H (Paragraph[0022]) (S2). CPU 211 stores the cable TV program data (e.g., Cable TVProgram Data#1 Through #4) in Cable TV Program Data Storage Area 20694b3(Paragraph [0260]) (S3). The foregoing sequence is repeatedperiodically.

Paragraph [0268]—<<Multiple TV Screen Displaying Function>>

Paragraph [0269]—Paragraph [0270] through Paragraph [0295] illustrate(s)the multiple TV screen displaying function which displays a plurality ofTV screen on LCD 201 (FIG. 1) of Communication Device 200 wherein eachTV screen displays a TV program, and the user of Communication Device200 is enabled to select a TV program to watch therefrom.

Paragraph [0270]—This Paragraph [0270] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Communication Device 200. In the presentembodiment, RAM 206 includes Multiple TV Screen Displaying InformationStorage Area 20695a of which the data and the software programs storedtherein are described in Paragraph [0272].

Paragraph [0271]—The data and/or the software programs stored inMultiple TV Screen Displaying Information Storage Area 20695a (Paragraph[0270]) may be downloaded from Host H (Paragraph [0022]) in the mannerdescribed in Paragraph [0416] through Paragraph [0422].

Paragraph [0272]—This Paragraph [0272] illustrate(s) the storage areasincluded in Multiple TV Screen Displaying Information Storage Area20695a (Paragraph [0270]). In the present embodiment, Multiple TV ScreenDisplaying Information Storage Area 20695a includes Multiple TV ScreenDisplaying Data Storage Area 20695b and Multiple TV Screen DisplayingSoftware Storage Area 20695c. Multiple TV Screen Displaying Data StorageArea 20695b stores the data necessary to implement the present functionon the side of Communication Device 200, such as the ones described inParagraph [0273] through Paragraph [0276]. Multiple TV Screen DisplayingSoftware Storage Area 20695c stores the software programs necessary toimplement the present function on the side of Communication Device 200,such as the ones described in Paragraph [0277].

Paragraph [0273]—This Paragraph [0273] illustrate(s) the storage areasincluded in Multiple TV Screen Displaying Data Storage Area 20695b(Paragraph [0272]). In the present embodiment, Multiple TV ScreenDisplaying Data Storage Area 20695b includes TV Program Data StorageArea 20695b1, Multiple TV Screen Data Storage Area 20695b2, and WorkArea 20695b3. TV Program Data Storage Area 20695b1 stores the datadescribed in Paragraph [0274]. Multiple TV Screen Data Storage Area20695b2 stores the data described in Paragraph [0275]. Work Area 20695b3is utilized as a work area to perform calculation and temporarily storedata.

Paragraph [0274]—This Paragraph [0274] illustrate(s) the data stored inTV Program Data Storage Area 20695b1 (Paragraph [0273]). In the presentembodiment, TV Program Data Storage Area 20695b1 comprises two columns,i.e., ‘TV Program ID’ and ‘TV Program Data’. Column ‘TV Program ID’stores the TV program IDs, and each TV program ID is an identificationof the corresponding TV program data stored in column TV Program Data'.Column ‘TV Program Data’ stores the TV program data, and each TV programdata is a TV program data including audiovisual data designed to beoutput from LCD 201 (FIG. 1) and Speaker 216 (FIG. 1) of CommunicationDevice 200. Here, the TV program data may be of the data utilized and/ormay be stored in Communication Device 200 in the manner described in thefunction(s) and/or system(s) described in this specification, such asthe multiple type TV program distributing system (Paragraph [0243]through Paragraph [0267]). In the present embodiment, TV Program DataStorage Area 20695b1 stores the following data: the TV program ID ‘TVProgram#1’ and the corresponding TV program data ‘TV Program Data#1’;the TV program ID ‘TV Program#2’ and the corresponding TV program data‘TV Program Data#2’; the TV program ID ‘TV Program#3’ and thecorresponding TV program data ‘TV Program Data#3; and the TV program IDTV Program#4’ and the corresponding TV program data ‘TV Program Data#4’.

Paragraph [0275]—This Paragraph [0275] illustrate(s) the data stored inMultiple TV Screen Data Storage Area 20695b2 (Paragraph [0273]). In thepresent embodiment, Multiple TV Screen Data Storage Area 20695b2comprises two columns, i.e., ‘Cell ID’ and ‘TV Program Data DisplayingCell’. Column ‘Cell ID’ stores the cell IDs, and each cell ID is anidentification of the corresponding TV program data displaying cellstored in column TV Program Data Displaying Cell'. Column ‘TV ProgramData Displaying Cell’ stores the TV program data displaying cell, andeach TV program data displaying cell is the area in which a TV programdata stored in TV Program Data Storage Area 20695b1 (Paragraph [0274])is temporary stored and from which the TV program data is retrieved forpurposes of being displayed on LCD 201 (FIG. 1) of Communication Device200. In the present embodiment, Multiple TV Screen Data Storage Area20695b2 stores the following data: the cell ID ‘Cell#1’ and thecorresponding TV program data displaying cell TV Program Data DisplayingCell#1; the cell ID ‘Cell#2’ and the corresponding TV program datadisplaying cell ‘TV Program Data Displaying Cell#2’; the cell ID‘Cell#3’ and the corresponding TV program data displaying cell ‘TVProgram Data Displaying Cell#3’; and the cell ID ‘Cell#4’ and thecorresponding TV program data displaying cell ‘TV Program DataDisplaying Cell#4’.

Paragraph [0276]—This Paragraph [0276] illustrate(s) the location ofeach TV program data displaying cell described in the previousembodiment. In the present embodiment, each TV program data displayingcell is arranged in a matrix fashion.

Paragraph [0277]—This Paragraph [0277] illustrate(s) the softwareprograms stored in Multiple TV Screen Displaying Software Storage Area20695c (Paragraph [0272]). In the present embodiment, Multiple TV ScreenDisplaying Software Storage Area 20695c stores Multiple TV ProgramRetrieving Software 20695c1, Multiple TV Program Displaying Software20695c2, TV Program Selecting Software 20695c3, and Multiple TV ProgramMatrix Data Displaying Software 20695c5. Multiple TV Program RetrievingSoftware 20695c1 is the software program described in Paragraph [0278].Multiple TV Program Displaying Software 20695c2 is the software programdescribed in Paragraph [0280]. TV Program Selecting Software 20695c3 isthe software program described in Paragraph [0281]. Multiple TV ProgramMatrix Data Displaying Software 20695c5 is the software programdescribed in Paragraph [0293].

Paragraph [0278]—This Paragraph [0278] illustrate(s) Multiple TV ProgramRetrieving Software 20695c1 (Paragraph [0277]) of Communication Device200, which retrieves all TV program data from TV Program Data StorageArea 20695b1 (Paragraph [0274]). In the present embodiment, CPU 211(FIG. 1) of Communication Device 200 retrieves TV Program Data#1 through#4 from TV Program Data Storage Area 20695b1 (Paragraph [0274]) (S1).CPU 211 stores TV Program Data#1 in TV Program Data Displaying Cell#1 ofMultiple TV Screen Data Storage Area 20695b2 (Paragraph [0275]) (S2).CPU 211 stores TV Program Data#2 in TV Program Data Displaying Cell#2 ofMultiple TV Screen Data Storage Area 20695b2 (Paragraph [0275]) (S3).CPU 211 stores TV Program Data#3 in TV Program Data Displaying Cell#3 ofMultiple TV Screen Data Storage Area 20695b2 (Paragraph [0275]) (S4).CPU 211 stores TV Program Data#4 in TV Program Data Displaying Cell#4 ofMultiple TV Screen Data Storage Area 20695b2 (Paragraph [0275]) (S5).

Paragraph [0279]—This Paragraph [0279] illustrate(s) the display areasat which the TV program data are displayed. In the present embodiment,each TV program data stored in Multiple TV Screen Data Storage Area20695b2 (Paragraph [0275]) is retrieved and displayed on LCD 201(FIG. 1) of Communication Device 200 in a matrix fashion. Namely, TVProgram Data#1 stored in TV Program Data Displaying Cell#1 of MultipleTV Screen Data Storage Area 20695b2 (Paragraph [0275]) is displayed atDisplay Area 20195a; TV Program Data#2 stored in TV Program DataDisplaying Cell#2 of Multiple TV Screen Data Storage Area 20695b2 isdisplayed at Display Area 20195b; TV Program Data#3 stored in TV ProgramData Displaying Cell#3 of Multiple TV Screen Data Storage Area 20695b2is displayed at Display Area 20195c; and TV Program Data#4 stored in TVProgram Data Displaying Cell#4 of Multiple TV Screen Data Storage Area20695b2 is displayed at Display Area 20195d.

Paragraph [0280]—This Paragraph [0280] illustrate(s) Multiple TV ProgramDisplaying Software 20695c2 (Paragraph [0277]) of Communication Device200, which displays the TV program data stored in Multiple TV ScreenData Storage Area 20695b2 (Paragraph [0275]) in a matrix fashion. In thepresent embodiment, CPU 211 (FIG. 1) of Communication Device 200retrieves TV Program Data#1 from TV Program Data Displaying WW1 ofMultiple TV Screen Data Storage Area 20695b2 (Paragraph [0275]) anddisplays the data at Display Area 20195a (Paragraph [0279]) (S1). CPU211 retrieves TV Program Data#2 from TV Program Data Displaying Cell#2of Multiple TV Screen Data Storage Area 20695b2 (Paragraph [0275]) anddisplays the data at Display Area 20195b (Paragraph [0279]) (S2). CPU211 retrieves TV Program Data#3 from TV Program Data Displaying Cell#3of Multiple TV Screen Data Storage Area 20695b2 (Paragraph [0275]) anddisplays the data at Display Area 20195c (Paragraph [0279]) (S3). CPU211 retrieves TV Program Data#4 from TV Program Data Displaying Cell#4of Multiple TV Screen Data Storage Area 20695b2 (Paragraph [0275]) anddisplays the data at Display Area 20195d (Paragraph [0279]) (S4).

Paragraph [0281]—This Paragraph [0281] illustrate(s) TV ProgramSelecting Software 20695c3 (Paragraph [0277]) of Communication Device200, which selects a TV program in order for the TV program to bedisplayed on LCD 201 (FIG. 1) in full screen. Referring to the presentembodiment, the user of Communication Device 200 selects a display area(e.g., Display Area 20195a) by utilizing Input Device 210 (FIG. 1) orvia voice recognition system (S1). CPU 211 (FIG. 1) of CommunicationDevice 200 displays the TV program data (e.g., TV Program Data#1)displayed in display area (e.g., Display Area 20195a) selected in S1 infull screen (S2).

Paragraph [0282]—<<Multiple TV Screen Displaying Function—AnotherEmbodiment>>

Paragraph [0283]—Paragraph [0284] through Paragraph [0295] illustrate(s)another embodiment, wherein Host H (Paragraph [0022]) plays a major rolein implementing the present function.

Paragraph [0284]—This Paragraph [0284] illustrate(s) the storage areaincluded in Host H (Paragraph [0022]). In the present embodiment, Host Hincludes Multiple TV Screen Displaying Information Storage Area H95a ofwhich the data and the software programs stored therein are described inParagraph [0285].

Paragraph [0285]—This Paragraph [0285] illustrate(s) the storage areasincluded in Multiple TV Screen Displaying Information Storage Area H95a(Paragraph [0284]). In the present embodiment, Multiple TV ScreenDisplaying Information Storage Area H95a includes Multiple TV ScreenDisplaying Data Storage Area H95b and Multiple TV Screen DisplayingSoftware Storage Area H95c. Multiple TV Screen Displaying Data StorageArea H95b stores the data necessary to implement the present function onthe side of Host H (Paragraph [0022]), such as the ones described inParagraph [0286] through Paragraph [0289]. Multiple TV Screen DisplayingSoftware Storage Area H95c stores the software programs necessary toimplement the present function on the side of Host H, such as the onesdescribed in Paragraph [0290].

Paragraph [0286]—This Paragraph [0286] illustrate(s) the storage areasincluded in Multiple TV Screen Displaying Data Storage Area H95b(Paragraph [0285]). In the present embodiment, Multiple TV ScreenDisplaying Data Storage Area H95b includes TV Program Data Storage AreaH95b1, Multiple TV Screen Data Storage Area H95b2, and Work Area H95b3.TV Program Data Storage Area H95b1 stores the data described inParagraph [0287]. Multiple TV Screen Data Storage Area H95b2 stores thedata described in Paragraph [0288]. Work Area H95b3 is utilized as awork area to perform calculation and temporarily store data.

Paragraph [0287]—This Paragraph [0287] illustrate(s) the data stored inTV Program Data Storage Area H95b1 (Paragraph [0286]). In the presentembodiment, TV Program Data Storage Area H95b1 comprises two columns,i.e., ‘TV Program ID’ and TV Program Data'. Column ‘TV Program ID’stores the TV program IDs, and each TV each TV program ID is anidentification of the corresponding TV program data stored in column ‘TVProgram Data’. Column ‘TV Program Data’ stores the TV program data, andeach TV program data is a TV program data including audiovisual datadesigned to be output from LCD 201 (FIG. 1) and Speaker 216 (FIG. 1) ofCommunication Device 200. Here, the TV program data may be of the datautilized and/or may be stored in Host H (Paragraph [0022]) in the mannerdescribed in the function(s) and/or system(s) described in thisspecification, such as the multiple type TV program distributing system(Paragraph [0243] through Paragraph [0267]). In the present embodiment,TV Program Data Storage Area H95b1 stores the following data: the TVprogram ID ‘TV Program#1’ and the corresponding TV program data ‘TVProgram Data#1’; the TV program ID ‘TV Program#2’ and the correspondingTV program data ‘TV Program Data#2’; the TV program ID ‘TV Program#3’and the corresponding TV program data ‘TV Program Data#3’; and the TVprogram ID ‘TV Program#4’ and the corresponding TV program data ‘TVProgram Data#4’.

Paragraph [0288]—This Paragraph [0288] illustrate(s) the data stored inMultiple TV Screen Data Storage Area H95b2 (Paragraph [0286]). In thepresent embodiment, Multiple TV Screen Data Storage Area H95b2 comprisestwo columns, i.e., ‘Cell ID’ and ‘TV Program Data Displaying Cell’.Column ‘Cell ID’ stores the cell IDs, and each cell ID is anidentification of the corresponding TV program data displaying cellstored in column ‘TV Program Data Displaying Cell’. Column ‘TV ProgramData Displaying Cell’ stores the TV program data displaying cell, andeach TV program data displaying cell is the area in which a TV programdata stored in TV Program Data Storage Area H95b1 (Paragraph [0287]) istemporary stored and from which the TV program data is retrieved forpurposes of being displayed on LCD 201 (FIG. 1) of Communication Device200. In the present embodiment, Multiple TV Screen Data Storage AreaH95b2 stores the following data: the cell ID ‘Cell#1’ and thecorresponding TV program data displaying cell ‘TV Program DataDisplaying Cell#1’; the cell ID ‘Cell#2’ and the corresponding TVprogram data displaying cell ‘TV Program Data Displaying Cell#2’; thecell ID ‘Cell#3’ and the corresponding TV program data displaying cell‘TV Program Data Displaying Cell#3’; and the cell ID ‘Cell#4’ and thecorresponding TV program data displaying cell ‘TV Program DataDisplaying Cell#4’.

Paragraph [0289]—This Paragraph [0289] illustrate(s) the location ofeach TV program data displaying cell described in the previousembodiment. In the present embodiment, each TV program data displayingcell is arranged in a matrix fashion.

Paragraph [0290]—This Paragraph [0290] illustrate(s) the softwareprograms stored in Multiple TV Screen Displaying Software Storage AreaH95c (Paragraph [0285]). In the present embodiment, Multiple TV ScreenDisplaying Software Storage Area H95c stores Multiple TV ProgramRetrieving Software H95c1, TV Program Selecting Software H95c3, MultipleTV Program Matrix Data Producing Software H95c4, and Multiple TV ProgramMatrix Data Displaying Software H95c5. Multiple TV Program RetrievingSoftware H95c1 is the software program described in Paragraph [0291]. TVProgram Selecting Software H95c3 is the software program described inParagraph [0295]. Multiple TV Program Matrix Data Producing SoftwareH95c4 is the software program described in Paragraph [0292]. Multiple TVProgram Matrix Data Displaying Software H95c5 is the software programdescribed in Paragraph [0293].

Paragraph [0291]—This Paragraph [0291] illustrate(s) Multiple TV ProgramRetrieving Software H95c1 (Paragraph [0290]) of Host H (Paragraph[0022]), which retrieves all TV program data from TV Program DataStorage Area H95b1 (Paragraph [0287]). In the present embodiment, Host Hretrieves TV Program Data#1 through #4 from TV Program Data Storage AreaH95b1 (Paragraph [0287]) (S1). Host H stores TV Program Data#1 in TVProgram Data Displaying Cell#1 of Multiple TV Screen Data Storage AreaH95b2 (Paragraph [0288]) (S2). Host H stores TV Program Data#2 in TVProgram Data Displaying Cell#2 of Multiple TV Screen Data Storage AreaH95b2 (Paragraph [0288]) (S3). Host H stores TV Program Data#3 in TVProgram Data Displaying Cell#3 of Multiple TV Screen Data Storage AreaH95b2 (Paragraph [0288]) (S4). Host H stores TV Program Data#4 in TVProgram Data Displaying Cell#4 of Multiple TV Screen Data Storage AreaH95b2 (Paragraph [0288]) (S5). The foregoing sequence is repeatedperiodically.

Paragraph [0292]—This Paragraph [0292] illustrate(s) Multiple TV ProgramMatrix Data Producing Software H95c4 (Paragraph [0290]) of Host H(Paragraph [0022]), which displays the TV program data stored inMultiple TV Screen Data Storage Area H95b2 (Paragraph [0288]) in amatrix fashion. In the present embodiment, Host H retrieves TV ProgramData#1 from TV Program Data Displaying Cell#1 of Multiple TV Screen DataStorage Area H95b2 (Paragraph [0288]) (S1). Host H retrieves TV ProgramData#2 from TV Program Data Displaying Cell#2 of Multiple TV Screen DataStorage Area H95b2 (Paragraph [0288]) (S2). Host H retrieves TV ProgramData#3 from TV Program Data Displaying Cell#3 of Multiple TV Screen DataStorage Area H95b2 (Paragraph [0288]) (S3). Host H retrieves TV ProgramData#4 from TV Program Data Displaying Cell#4 of Multiple TV Screen DataStorage Area H95b2 (Paragraph [0288]) (S4). Host H produces a multipleTV program matrix data and stores the data in Work Area H95b3 (Paragraph[0286]) (S5). Here, the multiple TV program matrix data is a visual dataproduced by composing TV Program Data#1 through #4 into one screen datadesigned to be displayed on LCD 201 (FIG. 1) as described in Paragraph[0294]. The foregoing sequence is repeated periodically.

Paragraph [0293]—This Paragraph [0293] illustrate(s) Multiple TV ProgramMatrix Data Displaying Software H95c5 (Paragraph [0290]) of Host H(Paragraph [0022]) and Multiple TV Program Matrix Data DisplayingSoftware 20695c5 (Paragraph [0277]) of Communication Device 200, whichdisplay the multiple TV program matrix data on LCD 201 (FIG. 1). In thepresent embodiment, Host H retrieves the multiple TV program matrix datafrom Work Area H95b3 (Paragraph [0286]) and sends the data toCommunication Device 200 (S1). CPU 211 (FIG. 1) of Communication Device200 receives the multiple TV program matrix data from Host H and storesthe data in Work Area 20695b3 (Paragraph [0273]) (S2). The foregoingsequence is repeated periodically.

Paragraph [0294]—This Paragraph [0294] illustrate(s) the multiple TVprogram matrix data displayed on LCD 201 (FIG. 1). In the presentembodiment, the TV program data stored in Multiple TV Screen DataStorage Area H95b2 of Host H (Paragraph [0022]) are displayed on LCD 201(FIG. 1) of Communication Device 200 in a matrix fashion. Namely, TVProgram Data#1 stored in TV Program Data Displaying Cell#1 of MultipleTV Screen Data Storage Area H95b2 (Paragraph [0288]) is displayed atDisplay Area 20195a; TV Program Data#2 stored in TV Program DataDisplaying Cell#2 of Multiple TV Screen Data Storage Area H95b2 isdisplayed at Display Area 20195b; TV Program Data#3 stored in TV ProgramData Displaying Cell#3 of Multiple TV Screen Data Storage Area H95b2 isdisplayed at Display Area 20195c; and TV Program Data#4 stored in TVProgram Data Displaying Cell#4 of Multiple TV Screen Data Storage AreaH95b2 is displayed at Display Area 20195d.

Paragraph [0295]—This Paragraph [0295] illustrate(s) TV ProgramSelecting Software H95c3 (Paragraph [0290]) of Host H (Paragraph [0022])and TV Program Selecting Software 20695c3 (Paragraph [0277]) ofCommunication Device 200, which select a TV program in order for the TVprogram to be displayed on LCD 201 (FIG. 1) in full screen. In thepresent embodiment, the user of Communication Device 200 selects adisplay area (e.g., Display Area 20195a) by utilizing Input Device 210(FIG. 1) or via voice recognition system (S1). CPU 211 (FIG. 1) ofCommunication Device 200 sends a selected display area signal, which isreceived by Host H (S2). Here, the selected display area signal is asignal identifying the display area (e.g., Display Area 20195a) selectedin the previous step. Host H identifies the corresponding TV programdata (e.g., TV Program Data#1) and retrieves the data which is sent toCommunication Device 200 (S3). CPU 211 receives the TV program data(e.g., TV Program Data#1) and stores the data in Work Area 20695b3(Paragraph [0273]) (S4). CPU 211 retrieves the TV program data (e.g., TVProgram Data#1) from Work Area 20695b3 (Paragraph [0273]) and displaysthe data on LCD 201 (FIG. 1) in full screen (S5).

Paragraph [0296]—<<Communication Device Finding Function>>

Paragraph [0297]—This Paragraph [0297] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Communication Device 200. In the presentembodiment, RAM 206 includes Communication Device Finding InformationStorage Area 20697a of which the data and the software programs storedtherein are described in Paragraph [0299].

Paragraph [0298]—The data and/or the software programs stored inCommunication Device Finding Information Storage Area 20697a (Paragraph[0297]) may be downloaded from Host H (Paragraph [0022]) in the mannerdescribed in Paragraph [0416] through Paragraph [0422].

Paragraph [0299]—This Paragraph [0299] illustrate(s) the storage areasincluded in Communication Device Finding Information Storage Area 20697a(Paragraph [0297]). In the present embodiment, Communication DeviceFinding Information Storage Area 20697a includes Communication DeviceFinding Data Storage Area 20697b and Communication Device FindingSoftware Storage Area 20697c. Communication Device Finding Data StorageArea 20697b stores the data necessary to implement the present function,such as the ones described in Paragraph [0300]. Communication DeviceFinding Software Storage Area 20697c stores the software programsnecessary to implement the present function, such as the ones describedin Paragraph [0301].

Paragraph [0300]—This Paragraph [0300] illustrate(s) the storage areasincluded in Communication Device Finding Data Storage Area 20697b(Paragraph [0299]). In the present embodiment, Communication DeviceFinding Data Storage Area 20697b includes User's Voice Wave Data StorageArea 20697b1, User's Voice Pattern Data Storage Area 20697b2, User'sPhrase Data Storage Area 20697b3, Responding Sound Data Storage Area20697b4, and Work Area 20697b5. User's Voice Wave Data Storage Area20697b1 stores the user's voice wave data. Here, the user's voice wavedata is the wave data of the voice of the user of Communication Device200. User's Voice Pattern Data Storage Area 20697b2 stores the user'svoice pattern data. Here, the user's voice pattern data is the voicepattern data of the user of Communication Device 200. The voice patterndata is same or similar to voice print which is unique to each user.User's Phrase Data Storage Area 20697b3 stores the user's phrase data.Here, the user's phrase data is primarily composed of alphanumeric data.The phrase data may be a word or a sentence determined by the user ofCommunication Device 200. In the present example, a phrase ‘Where areyou, Communication Device 200?’ is stored in User's Phrase Data StorageArea 20697b3. Responding Sound Data Storage Area 20697b4 stores theresponding sound data. Here the responding sound data is the sound datadesigned to be output via Speaker 216 (FIG. 1) for responding purposes.The responding sound data may be any data which may be output fromSpeaker 216. Work Area 20697b5 is utilized as a work area to performcalculation and temporarily store data.

Paragraph [0301]—This Paragraph [0301] illustrate(s) the softwareprograms stored in Communication Device Finding Software Storage Area20697c (Paragraph [0299]). In the present embodiment, CommunicationDevice Finding Software Storage Area 20697c stores User's Voice WaveData Analyzing Software 20697c1 and Responding Sound Data OutputtingSoftware 20697c2. User's Voice Wave Data Analyzing Software 20697c1 isthe software program described in Paragraph [0302]. Responding SoundData Outputting Software 20697c2 is the software program described inParagraph [0303] and Paragraph [0304].

Paragraph [0302]—This Paragraph [0302] illustrate(s) User's Voice WaveData Analyzing Software 20697c1 (Paragraph [0301]) of CommunicationDevice 200, which retrieves the user's voice pattern data and the user'sphrase data from the user's voice wave data. In the present embodiment,the user of Communication Device 200 inputs the user's voice wave datavia Microphone 215 (FIG. 1) (S1). CPU 211 (FIG. 1) of CommunicationDevice 200 stores the user's voice wave data in User's Voice Wave DataStorage Area 20697b1 (Paragraph [0300]) (S2). CPU 211 retrieves theuser's voice pattern data from the user's voice wave data, and storesthe data in User's Voice Pattern Data Storage Area 20697b2 (Paragraph[0300]) (S3). CPU 211 retrieves the user's phrase data by voicerecognition system, and stores the data in User's Phrase Data StorageArea 20697b3 (Paragraph [0300]) (S4).

Paragraph [0303]—This Paragraph [0303] illustrate(s) Responding SoundData Outputting Software 20697c2 (Paragraph [0301]) of CommunicationDevice 200, which outputs the responding sound data when a predetermineduser's voice data is detected. In the present embodiment, CPU 211(FIG. 1) of Communication Device 200 retrieves the general sound datavia Microphone 215 (FIG. 1) (S1). CPU 211 stores the general sound dataretrieved in the previous step in Work Area 20697b5 (Paragraph [0300])(S2). CPU 211 retrieves the pattern data from the general sound data,and compares the data with the user's voice pattern data stored inUser's Voice Pattern Data Storage Area 20697b2 (Paragraph [0300]) (S3).If the pattern data of the general sound data substantially matches withthe user's voice pattern data, CPU 211 retrieves the alphanumeric datatherefrom by utilizing voice recognition system described hereinbefore(S4). CPU 211 compares the alphanumeric data retrieved in the previousstep with the user's phrase data stored in User's Phrase Data StorageArea 20697b3 (Paragraph [0300]) (S5). If the two data in the previousstep substantially matches, CPU 211 retrieves the responding sound datafrom Responding Sound Data Storage Area 20697b4 (Paragraph [0300]), andoutputs the responding sound data from Speaker 216 (FIG. 1) with maximumvolume (S6). The foregoing sequence is repeated periodically.

Paragraph [0304]—This Paragraph [0304] illustrate(s) Responding SoundData Outputting Software 20697c2 (Paragraph [0301]) of CommunicationDevice 200, which outputs the responding sound data when a predetermineduser's voice data is detected. The present embodiment illustrate(s)another embodiment of Responding Sound Data Outputting Software 20697c2described in the previous embodiment. In the present embodiment, CPU 211(FIG. 1) of Communication Device 200 retrieves the general sound datavia Microphone 215 (FIG. 1) (S1). CPU 211 stores the general sound dataretrieved in the previous step in Work Area 20697b5 (Paragraph [0300])(S2). CPU 211 retrieves the general sound data from Work Area 20697b5(Paragraph [0300]), and compares the data with the user's voice wavedata stored in User's Voice Wave Data Storage Area 20697b1 (Paragraph[0300]) (S3). If the two data in the previous step substantiallymatches, CPU 211 retrieves the responding sound data from RespondingSound Data Storage Area 20697b4 (Paragraph [0300]), and outputs theresponding sound data from Speaker 216 (FIG. 1) with maximum volume(S4). The foregoing sequence is repeated periodically.

Paragraph [0305]—<<Product Information Retrieving Function (CCD)>>

Paragraph [0306]—Paragraph [0307] through Paragraph [0327] illustrate(s)the product information retrieving function wherein an image dataattached to a product (such as the one sold in a supermarket) is inputvia CCD Unit 214 (FIG. 1) and a product data relating to the product isdisplayed on LCD 201 (FIG. 1) of Communication Device 200.

Paragraph [0307]—This Paragraph [0307] illustrate(s) the storage areaincluded in Host H (Paragraph [0022]). In the present embodiment, Host Hincludes Product Information Retrieving Information Storage Area H99a ofwhich the data and the software programs stored therein are described inParagraph [0308].

Paragraph [0308]—This Paragraph [0308] illustrate(s) the storage areasincluded in Product Information Retrieving Information Storage Area H99a(Paragraph [0307]). In the present embodiment, Product InformationRetrieving Information Storage Area H99a includes Product InformationRetrieving Data Storage Area H99b and Product Information RetrievingSoftware Storage Area H99c. Product Information Retrieving Data StorageArea H99b stores the data necessary to implement the present function onthe side of Host H (Paragraph [0022]), such as the ones described inParagraph [0309] through Paragraph [0311]. Product InformationRetrieving Software Storage Area H99c stores the software programsnecessary to implement the present function on the side of Host H, suchas the ones described in Paragraph [0312].

Paragraph [0309]—This Paragraph [0309] illustrate(s) the storage areasincluded in Product Information Retrieving Data Storage Area H99b(Paragraph [0308]). In the present embodiment, Product InformationRetrieving Data Storage Area H99b includes Product Data Storage AreaH99b1, Encrypted Image Data Storage Area H99b2, and Work Area H99b3.Product Data Storage Area H99b1 stores the data described in Paragraph[0310]. Encrypted Image Data Storage Area H99b2 stores the datadescribed in Paragraph [0311]. Work Area H99b3 is utilized as a workarea to perform calculation and temporarily store data.

Paragraph [0310]—This Paragraph [0310] illustrate(s) the data stored inProduct Data Storage Area H99b1 (Paragraph [0309]). In the presentembodiment, Product Data Storage Area H99b1 comprises two columns, i.e.,‘Product ID’ and ‘Product Data’. Column ‘Product ID’ stores the productIDs, and each product ID is an identification of the correspondingproduct data stored in column ‘Product Data’. Column ‘Product Data’stores the product data, and each product data includes various types ofdata of a specific product. Here, the product data includes, in thepresent example, the product name data, the produced date data, theprice data, the producer's name data, the produced country data, and/orthe ingredient data. Here, the product name data represents the name ofthe corresponding product; the produced date data represents the date atwhich the corresponding product is produced; the price data representsthe price with which the corresponding product is sold; the producer'sname data represents the name of the producer (or manufacturer) whoproduced (or manufactured) the corresponding product; the producedcountry data represents the name of the country at which thecorresponding product is produced (or manufactured); and the ingredientdata represents the ingredients included in the corresponding product.In the present embodiment, Product Data Storage Area H99b1 stores thefollowing data: the product ID ‘Product#1’ and the corresponding productdata ‘Product Data#1’; the product ID ‘Product#2’ and the correspondingproduct data ‘Product Data#2’; the product ID ‘Product#3’ and thecorresponding product data ‘Product Data#3’; and the product ID‘Product#4’ and the corresponding product data ‘Product Data#4’. Theproduct data ‘Product Data#1’ represents the product data of a babyfood; the product data ‘Product Data#2’ represents the product data of asoap; the product data ‘Product Data#3’ represents the product data of adish; and the product data ‘Product Data#4’ represents the product dataof a can juice.

Paragraph [0311]—This Paragraph [0311] illustrate(s) the data stored inEncrypted Image Data Storage Area H99b2 (Paragraph [0309]). In thepresent embodiment, Encrypted Image Data Storage Area H99b2 comprisestwo columns, i.e., ‘Product ID’ and ‘Encrypted Image Data’. Column‘Product ID’ stores the product IDs, and each product ID is anidentification of the corresponding encrypted image data stored incolumn ‘Encrypted Image Data’. The product IDs stored in Encrypted ImageData Storage Area H99b2 (Paragraph [0311]) are identical to the onesstored in Product Data Storage Area H99b1 (Paragraph [0310]). Column‘Encrypted Image Data’ stores the encrypted image data, and eachencrypted image data is an image data from which the product data cannot be visually perceived. Bar code may be utilized for the encryptedimage data. The encrypted image data may be constituted of two colors(i.e., black and white) or include more than two colors (i.e., blue,green, red, black, white, yellow, and brown). The encrypted image datamay be constituted of a set of stripes, dots, and/or specific patterns.In the present embodiment, Encrypted Image Data Storage Area H99b2stores the following data: the product ID ‘Product#1’ and thecorresponding encrypted image data ‘Encrypted Image Data#1’; the productID ‘Product#2’ and the corresponding encrypted image data ‘EncryptedImage Data#2’; the product ID ‘Product#3’ and the correspondingencrypted image data ‘Encrypted Image Data#3’; and the product ID‘Product#4’ and the corresponding encrypted image data ‘Encrypted ImageData#4’.

Paragraph [0312]—This Paragraph [0312] illustrate(s) the softwareprograms stored in Product Information Retrieving Software Storage AreaH99c (Paragraph [0308]). In the present embodiment, Product InformationRetrieving Software Storage Area H99c stores Product Data DisplayingSoftware H99c2 and Product Data/Encrypted Image Data Updating SoftwareH99c3. Product Data Displaying Software H99c2 is the software programdescribed in Paragraph [0327]. Product Data/Encrypted Image DataUpdating Software H99c3 is the software program described in Paragraph[0325].

Paragraph [0313]—This Paragraph [0313] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Communication Device 200. In the presentembodiment, RAM 206 includes Product Information Retrieving InformationStorage Area 20699a of which the data and the software programs storedtherein are described in Paragraph [0315].

Paragraph [0314]—The data and/or the software programs stored in ProductInformation Retrieving Information Storage Area 20699a (Paragraph[0313]) may be downloaded from Host H (Paragraph [0022]) in the mannerdescribed in Paragraph [0416] through Paragraph [0422].

Paragraph [0315]—This Paragraph [0315] illustrate(s) the storage areasincluded in Product Information Retrieving Information Storage Area20699a (Paragraph [0313]). In the present embodiment, ProductInformation Retrieving Information Storage Area 20699a includes ProductInformation Retrieving Data Storage Area 20699b and Product InformationRetrieving Software Storage Area 20699c. Product Information RetrievingData Storage Area 20699b stores the data necessary to implement thepresent function on the side of Communication Device 200, such as theones described in Paragraph [0316] through Paragraph [0318]. ProductInformation Retrieving Software Storage Area 20699c stores the softwareprograms necessary to implement the present function on the side ofCommunication Device 200, such as the ones described in Paragraph[0319].

Paragraph [0316]—This Paragraph [0316] illustrate(s) the storage areasincluded in Product Information Retrieving Data Storage Area 20699b(Paragraph [0315]). In the present embodiment, Product InformationRetrieving Data Storage Area 20699b includes Product Data Storage Area20699b1, Encrypted Image Data Storage Area 20699b2, and Work Area20699b3. Product Data Storage Area 20699b1 stores the data described inParagraph [0317]. Encrypted Image Data Storage Area 20699b2 stores thedata described in Paragraph [0318]. Work Area 20699b3 is utilized as awork area to perform calculation and temporarily store data.

Paragraph [0317]—This Paragraph [0317] illustrate(s) the data stored inProduct Data Storage Area 20699b1 (Paragraph [0316]). In the presentembodiment, Product Data Storage Area 20699b1 comprises two columns,i.e., ‘Product ID’ and ‘Product Data’. Column ‘Product ID’ stores theproduct IDs, and each product ID is an identification of thecorresponding product data stored in column ‘Product Data’. Column‘Product Data’ stores the product data, and each product data includesvarious types of data of a specific product. Here, the product dataincludes, in the present example, the product name data, the produceddate data, the price data, the producer's name data, the producedcountry data, and/or the ingredient data. Here, the product name datarepresents the name of the corresponding product; the produced date datarepresents the date at which the corresponding product is produced; theprice data represents the price with which the corresponding product issold; the producer's name data represents the name of the producer (ormanufacturer) who produced (or manufactured) the corresponding product;the produced country data represents the name of the country at whichthe corresponding product is produced (or manufactured); and theingredient data represents the ingredients included in the correspondingproduct. In the present embodiment, Product Data Storage Area 20699b1stores the following data: the product ID ‘Product#1’ and thecorresponding product data ‘Product Data#1’; the product ID ‘Product#2’and the corresponding product data ‘Product Data#2’; the product ID‘Product#3’ and the corresponding product data ‘Product Data#3’; and theproduct ID ‘Product#4’ and the corresponding product data ‘ProductData#4’. The product data ‘Product Data#1’ represents the product dataof a baby food; the product data ‘Product Data#2’ represents the productdata of a soap; the product data ‘Product Data#3’ represents the productdata of a dish; and the product data ‘Product Data#4’ represents theproduct data of a can juice.

Paragraph [0318]—This Paragraph [0318] illustrate(s) the data stored inEncrypted Image Data Storage Area 20699b2 (Paragraph [0316]). In thepresent embodiment, Encrypted Image Data Storage Area 20699b2 comprisestwo columns, i.e., ‘Product ID’ and ‘Encrypted Image Data’. Column‘Product ID’ stores the product IDs, and each product ID is anidentification of the corresponding encrypted image data stored incolumn ‘Encrypted Image Data’. The product IDs stored in Encrypted ImageData Storage Area H99b2 (Paragraph [0311]) are identical to the onesstored in Product Data Storage Area H99b1 (Paragraph [0310]). Column‘Encrypted Image Data’ stores the encrypted image data, and eachencrypted image data is an image data from which the product data cannot be visually perceived. Bar code may be utilized for the encryptedimage data. The encrypted image data may be constituted of two colors(i.e., black and white) or include more than two colors (i.e., blue,green, red, black, white, yellow, and brown). The encrypted image datamay be constituted of a set of stripes, dots, and/or specific patterns.In the present embodiment, Encrypted Image Data Storage Area 20699b2stores the following data: the product ID ‘Product#1’ and thecorresponding encrypted image data ‘Encrypted Image Data#1’; the productID ‘Product#2’ and the corresponding encrypted image data ‘EncryptedImage Data#2’; the product ID ‘Product#3’ and the correspondingencrypted image data ‘Encrypted Image Data#3’; and the product ID‘Product#4’ and the corresponding encrypted image data ‘Encrypted ImageData#4’.

Paragraph [0319]—This Paragraph [0319] illustrate(s) the softwareprograms stored in Product Information Retrieving Software Storage Area20699c (Paragraph [0315]). In the present embodiment, ProductInformation Retrieving Software Storage Area 20699c stores Image DataRetrieving Software 20699c1, Product Data Displaying Software 20699c2,and Product Data/Encrypted Image Data Updating Software 20699c3. ImageData Retrieving Software 20699c1 is the software program described inParagraph [0321]. Product Data Displaying Software 20699c2 is thesoftware program described in Paragraph [0327]. Product Data/EncryptedImage Data Updating Software 20699c3 is the software program describedin Paragraph [0325].

Paragraph [0320]—This Paragraph [0320] illustrate(s) the label, LabelL99 (Paragraph [0320]) attached to a product, Product P99, sold in asupermarket. Here, Product P99 may be any product, such as baby food,soap, dish, can juice, and frozen food. Product P99 may also includepaper product utilized for adverting, e.g., leaflet, catalogue, poster,brochure, and flyer. Label L99 (Paragraph [0320]) may be attached toProduct P99. Label L99 (Paragraph [0320]) may be directly printed toProduct P99 instead. A specific image is printed on Label L99 (Paragraph[0320]) from which the product data can not be visually perceived. Barcode may be utilized for the specific image. The specific image may beconstituted of two colors (i.e., black and white) or include more thantwo colors (i.e., blue, green, red, black, white, yellow, and brown).The specific image may be constituted of a set of stripes, dots, and/orspecific patterns.

Paragraph [0321]—This Paragraph [0321] illustrate(s) Image DataRetrieving Software 20699c1 (Paragraph [0319]) of Communication Device200, which retrieves the image data of Label L99 (Paragraph [0320]). Inthe present embodiment, CPU 211 (FIG. 1) of Communication Device 200retrieves the image data of Label L99 (Paragraph [0320]) via CCD Unit(FIG. 1) (S1). CPU 211 stores the image data retrieved in S1 in workarea 20699b3 (Paragraph [0316]) (S2).

Paragraph [0322]—This Paragraph [0322] illustrate(s) Product DataDisplaying Software H99c2 (Paragraph [0312]) of Host H (Paragraph[0022]) and the product data Displaying Software 20699c2 (Paragraph[0319]) of Communication Device 200, which display the product data ofProduct P99. In the present embodiment, CPU 211 (FIG. 1) ofCommunication Device 200 retrieves the image data from Work Area 20699b3(Paragraph [0316]) which is sent to Host H (S1). Host H receives theimage data from Communication Device 200 and stores the data in workarea H99b3 (Paragraph [0309]) (S2). Host H compares the image datastored in work area H99b3 (Paragraph [0309]) with the encrypted imagedata stored in Encrypted Image Data Storage Area H99b2 (Paragraph[0311]) (S3). If the matched encrypted image data is found in theprevious step, Host H identifies the corresponding product ID (S4). HostH identifies the product data stored in Product Data Storage Area H99b1(Paragraph [0310]) of the corresponding product ID (S5). Host H sendsthe product data identified in the previous step to Communication Device200, which is received by Communication Device 200 (S6). CPU 211 storesthe product data received in the previous step in work area 20699b3(Paragraph [0316]) and displays the data on LCD 201 (FIG. 1) (S7).

Paragraph [0323]—<<Product Information Retrieving Function (CCD)—AnotherEmbodiment>>

Paragraph [0324]—Paragraph [0325] through Paragraph [0327] illustrate(s)another embodiment, wherein Communication Device 200 plays the majorrole in implementing the present function.

Paragraph [0325]—This Paragraph [0325] illustrate(s) ProductData/Encrypted Image Data Updating Software H99c3 (Paragraph [0312]) ofHost H (Paragraph [0022]) and Product Data/Encrypted Image Data UpdatingSoftware 20699c3 (Paragraph [0319]) of Communication Device 200, whichupdate all data stored in Product Data Storage Area 20699b1 (Paragraph[0317]) and Encrypted Image Data Storage Area 20699b2 (Paragraph[0318]). In the present embodiment, CPU 211 (FIG. 1) of CommunicationDevice 200 sends the product data/encrypted image data updating request,which is received by Host H (S1). Here, the product data/encrypted imagedata updating request is a request sent to Host H to send all datastored in Product Data Storage Area H99b1 (Paragraph [0310]) andEncrypted Image Data Storage Area H99b2 (Paragraph [0311]) of Host H toCommunication Device 200. Host H retrieves all data stored in ProductData Storage Area H99b1 (Paragraph [0310]) and Encrypted Image DataStorage Area H99b2 (Paragraph [0311]) which are sent to CommunicationDevice 200 (S2). CPU 211 receives the data retrieved in the previousstep (S3). CPU 211 stores the product ID and the product data in ProductData Storage Area 20699b1 (Paragraph [0317]) (S4). CPU 211 stores theproduct ID and the encrypted image data in Encrypted Image Data StorageArea 20699b2 (Paragraph [0318]) (S5).

Paragraph [0326]—This Paragraph [0326] illustrate(s) Image DataRetrieving Software 20699c1 (Paragraph [0319]) of Communication Device200, which retrieves the image data of Label L99 (Paragraph [0320]). Inthe present embodiment, CPU 211 (FIG. 1) of Communication Device 200retrieves the image data of Label L99 (Paragraph [0320]) via CCD Unit(FIG. 1) (S1). CPU 211 stores the image data retrieved in S1 in workarea 20699b3 (Paragraph [0316]) (S2). Paragraph [0327]—This Paragraph[0327] illustrate(s) Product Data Displaying Software 20699c2 (Paragraph[0319]) of Communication Device 200, which displays the product data ofProduct P99. In the present embodiment, CPU 211 (FIG. 1) ofCommunication Device 200 retrieves the image data from Work Area 20699b3(Paragraph [0316]) (S1). CPU 211 compares the image data stored in workarea 20699b3 (Paragraph [0316]) with the encrypted image data stored inEncrypted Image Data Storage Area 20699b2 (Paragraph [0318]) (S2). Ifthe matched encrypted image data is found in the previous step, CPU 211identifies the corresponding product ID (S3). CPU 211 identifies theproduct data stored in Product Data Storage Area 20699b1 (Paragraph[0317]) of the corresponding product ID (S4). CPU 211 retrieves theproduct data identified in the previous step and displays the data onLCD 201 (FIG. 1) (S5).

Paragraph [0328]—<<Continue Enabled Video Game Function>>

Paragraph [0329]—Paragraph [0330] through Paragraph [0347] illustrate(s)the continue enabled video game function which enables a video game tobe continued from the point the game ended.

Paragraph [0330]—This Paragraph [0330] illustrate(s) the storage areaincluded in Host H (Paragraph [0022]). In the present embodiment, Host Hincludes Continue Enabled Video Game Information Storage Area H103a ofwhich the data and the software programs stored therein are described inParagraph [0331].

Paragraph [0331]—This Paragraph [0331] illustrate(s) the storage areasincluded in Continue Enabled Video Game Information Storage Area H103a(Paragraph [0330]). In the present embodiment, Continue Enabled VideoGame Information Storage Area H103a includes Continue Enabled Video GameData Storage Area H103b and Continue Enabled Video Game Software StorageArea H103c. Continue Enabled Video Game Data Storage Area H103b storesthe data necessary to implement the present function on the side of HostH (Paragraph [0022]), such as the ones described in Paragraph [0332].Continue Enabled Video Game Software Storage Area H103c stores thesoftware programs necessary to implement the present function on theside of Host H, such as the ones described in Paragraph [0333].

Paragraph [0332]—This Paragraph [0332] illustrate(s) the storage areasincluded in Continue Enabled Video Game Data Storage Area H103b(Paragraph [0331]). In the present embodiment, Continue Enabled VideoGame Data Storage Area H103b includes 3D Object Data Storage AreaH103b1, Count Down Data Storage Area H103b2, and Work Area H103b3. 3DObject Data Storage Area H103b1 stores the 3D object operable data, the3D object non-operable data, and the 3D background data. Here, the 3Dobject operable data represents the 3D object displayed on LCD 201(FIG. 1) which is capable to be manipulated by the user of CommunicationDevice 200. The 3D object non-operable data represents the 3D objectdisplayed on LCD 201 (FIG. 1) which is not capable to be manipulated bythe user of Communication Device 200. The 3D background data representsthe 3D object which is displayed on LCD 201 (FIG. 1) as a background(e.g., sky, clouds, buildings, and streets) of the corresponding videogame. Count Down Data Storage Area H103b2 stores the count down data.Here, the count down data is composed often count down image data, i.e.,the count down image ‘10’ data, the count down image ‘9’ data, the countdown image ‘8’ data, the count down image ‘7’ data, the count down image‘6’ data, the count down image ‘5’ data, the count down image ‘4’ data,the count down image ‘3’ data, the count down image ‘2’ data, and thecount down image ‘1’ data. The foregoing ten count down image data aredesigned to be displayed on LCD 201 (FIG. 1). Work Area H103b3 isutilized as a work area to perform calculation and temporarily storedata.

Paragraph [0333]—This Paragraph [0333] illustrate(s) the softwareprograms stored in Continue Enabled Video Game Software Storage AreaH103c (Paragraph [0331]). In the present embodiment, Continue EnabledVideo Game Software Storage Area H103c stores Video Game ProcessingSoftware H103c1, Video Game Continuing Software H103c2, and Video GameDownloading Software H103c3. Video Game Processing Software H103c1 isthe software program described in Paragraph [0339] and Paragraph [0345].Video Game Continuing Software H103c2 is the software program describedin Paragraph [0340] and Paragraph [0341], and Paragraph [0346] andParagraph [0347]. Video Game Downloading Software H103c3 is the softwareprogram described in Paragraph [0344].

Paragraph [0334]—This Paragraph [0334] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Communication Device 200. In the presentembodiment, RAM 206 includes Continue Enabled Video Game InformationStorage Area 206103a of which the data and the software programs storedtherein are described in Paragraph [0336].

Paragraph [0335]—The data and/or the software programs stored inContinue Enabled Video Game Information Storage Area 206103a (Paragraph[0334]) may be downloaded from Host H (Paragraph [0022]) in the mannerdescribed in Paragraph [0416] through Paragraph [0422].

Paragraph [0336]—This Paragraph [0336] illustrate(s) the storage areasincluded in Continue Enabled Video Game Information Storage Area 206103a(Paragraph [0334]). In the present embodiment, Continue Enabled VideoGame Information Storage Area 206103a includes Continue Enabled VideoGame Data Storage Area 206103b and Continue Enabled Video Game SoftwareStorage Area 206103c. Continue Enabled Video Game Data Storage Area206103b stores the data necessary to implement the present function onthe side of Communication Device 200, such as the ones described inParagraph [0337]. Continue Enabled Video Game Software Storage Area206103c stores the software programs necessary to implement the presentfunction on the side of Communication Device 200, such as the onesdescribed in Paragraph [0338].

Paragraph [0337]—This Paragraph [0337] illustrate(s) the storage areasincluded in Continue Enabled Video Game Data Storage Area 206103b(Paragraph [0336]). In the present embodiment, Continue Enabled VideoGame Data Storage Area 206103b includes 3D Object Data Storage Area206103b1, Count Down Data Storage Area 206103b2, and Work Area 206103b3.3D Object Data Storage Area 206103b1 stores the 3D object operable data,the 3D object non-operable data, and the 3D background data. Here, the3D object operable data represents the 3D object displayed on LCD 201(FIG. 1) which is capable to be manipulated by the user of CommunicationDevice 200. The 3D object non-operable data represents the 3D objectdisplayed on LCD 201 (FIG. 1) which is not capable to be manipulated bythe user of Communication Device 200. The 3D background data representsthe 3D object which is displayed on LCD 201 (FIG. 1) as a background(e.g., sky, clouds, buildings, and streets) of the corresponding videogame. Count Down Data Storage Area 206103b2 stores the count down data.Here, the count down data is composed of ten count down image data,i.e., the count down image ‘10’ data, the count down image ‘9’ data, thecount down image ‘8’ data, the count down image ‘7’ data, the count downimage ‘6’ data, the count down image ‘5’ data, the count down image ‘4’data, the count down image ‘3’ data, the count down image ‘2’ data, andthe count down image ‘1’ data. The foregoing ten count down image dataare designed to be displayed on LCD 201 (FIG. 1). Work Area 206103b3 isutilized as a work area to perform calculation and temporarily storedata.

Paragraph [0338]—This Paragraph [0338] illustrate(s) the softwareprograms stored in Continue Enabled Video Game Software Storage Area206103c (Paragraph [0336]). In the present embodiment, Continue EnabledVideo Game Software Storage Area 206103c stores Video Game ProcessingSoftware 206103c1, Video Game Continuing Software 206103c2, and VideoGame Downloading Software 206103c3. Video Game Processing Software206103c1 is the software program described in Paragraph [0339] andParagraph [0345]. Video Game Continuing Software 206103c2 is thesoftware program described in Paragraph [0340], and Paragraph [0346] andParagraph [0347]. Video Game Downloading Software 206103c3 is thesoftware program described in Paragraph [0344].

Paragraph [0339]—This Paragraph [0339] illustrate(s) Video GameProcessing Software H103c1 (Paragraph [0333]) of Host H (Paragraph[0022]) and Video Game Processing Software 206103c1 (Paragraph [0338])of Communication Device 200, which process the video game. Referring tothe present embodiment, CPU 211 (FIG. 1) of Communication Device 200sends a video game command signal which is received by Host H (S1).Here, the video game command signal is a signal input by utilizing InputDevice 210 (FIG. 1) or via voice recognition system to operate the 3Dobject operable data displayed on LCD 201 (FIG. 1). Host H retrieves the3D object operable data, the 3D object non-operable data, and the 3Dbackground data from 3D Object Data Storage Area H103b1 (Paragraph[0332]) (S2). Host H processes with the data retrieved in the previousstep in accordance with the video command signal received in S1 (S3).Host H produces the video game screen data, which is sent toCommunication Device 200 (S4). Here, the video game screen data is theimage data representing the perspective view of the 3D object operabledata, the 3D object non-operable data, and the 3D background dataretrieved in S2 after being processed in S3, which is designed to bedisplayed on LCD 201 (FIG. 1). CPU 211 receives the video game screendata and stores the data in Work Area 206103b3 (Paragraph [0337]), anddisplays the data on LCD 201 (FIG. 1) (S5). The foregoing sequence isrepeated periodically.

Paragraph [0340]—This Paragraph [0340] illustrate(s) Video GameContinuing Software H103c2 (Paragraph [0333]) of Host H (Paragraph[0022]) and Video Game Continuing Software 206103c2 (Paragraph [0338])of Communication Device 200, which continue and resume the video game.In the present embodiment, Host H periodically checks the game status(S1). If the game is over, Host H proceeds to the next step (S2). Host Hinitiates the video game continuing process (S3). If the video gamecontinuing signal is input during video game continuing process, Host Hproceeds to the next step (S4). Here, the video game continuing signalis a signal input by utilizing Input Device 210 (FIG. 1) or via voicerecognition system indicating to initiate the video game resumingprocess described in the next step. Host H initiates the video gameresuming process (S5). Here, the video game is continued and resumedfrom the point where the game ended. As another embodiment, if the videogame includes a plurality of game stages, and the game ended at a middleof a certain game stage, the video game is continued and resumed fromthe beginning of the game stage where the game ended.

Paragraph [0341]—This Paragraph [0341] illustrate(s) the video gamecontinuing process described in the previous embodiment. In the presentembodiment, Host H retrieves the count down image data (e.g., Count DownImage ‘10’ Data) from Count Down Data Storage Area H103b2 (Paragraph[0332]) (S1). Host H produces the video game screen data, which is sentto Communication Device 200 (S2). Here, the video game screen data isthe image data representing the perspective view of the 3D objectoperable data, 3D object non-operable data, and 3D background dataretrieved in S2 after being processed in S3, which is designed to bedisplayed on LCD 201 (FIG. 1). CPU 211 (FIG. 1) of Communication Device200 receives the video game screen data and stores the data in Work Area206103b3 (Paragraph [0337]), and displays the data on LCD 201 (FIG. 1)(S3). The foregoing sequence is repeated periodically. Thus, the countdown image ‘10’ data is displayed on LCD 201 (FIG. 1) for a certainperiod of time, the count down image ‘9’ data is displayed on LCD 201(FIG. 1) for a certain period of time, the count down image ‘8’ data isdisplayed on LCD 201 (FIG. 1) for a certain period of time, the countdown image ‘7’ data is displayed on LCD 201 (FIG. 1) for a certainperiod of time, the count down image ‘6’ data is displayed on LCD 201(FIG. 1) for a certain period of time, the count down image ‘5’ data isdisplayed on LCD 201 (FIG. 1) for a certain period of time, the countdown image ‘4’ data is displayed on LCD 201 (FIG. 1) for a certainperiod of time, the count down image ‘3’ data is displayed on LCD 201(FIG. 1) for a certain period of time, the count down image ‘2’ data isdisplayed on LCD 201 (FIG. 1) for a certain period of time, and thecount down image ‘1’ data is displayed on LCD 201 (FIG. 1) for a certainperiod of time.

Paragraph [0342]—<<Continue Enabled Video Game Function—AnotherEmbodiment>>

Paragraph [0343]—Paragraph [0344] through Paragraph [0347] illustrate(s)another embodiment, wherein the present function is implemented solelyby Communication Device 200.

Paragraph [0344]—This Paragraph [0344] illustrate(s) Video GameDownloading Software H103c3 (Paragraph [0333]) of Host H (Paragraph[0022]) and Video Game Downloading Software 206103c3 (Paragraph [0338])of Communication Device 200, which enable Communication Device 200 todownload a video game software capable to implement the presentfunction. In the present embodiment, Host H retrieves all data fromContinue Enabled Video Game Information Storage Area H103a (Paragraph[0330]), which is sent to Communication Device 200 (51). CPU 211(FIG. 1) of Communication Device 200 receives the data retrieved in theprevious step and stores the data in Continue Enabled Video GameInformation Storage Area 206103a (Paragraph [0334]) (S2).

Paragraph [0345]—This Paragraph [0345] illustrate(s) Video GameProcessing Software 206103c1 (Paragraph [0338]) of Communication Device200, which processes the video game. In the present embodiment, the userof Communication Device 200 inputs a video game command signal (S1).Here, the video game command signal is a signal input by utilizing InputDevice 210 (FIG. 1) or via voice recognition system to operate the 3Dobject operable data displayed on LCD 201 (FIG. 1). CPU 211 retrievesthe 3D object operable data, the 3D object non-operable data, and the 3Dbackground data from 3D Object Data Storage Area 206103b1 (Paragraph[0337]) (S2). CPU 211 processes with the data retrieved in the previousstep in accordance with the video command signal input in S1 (S3). CPU211 produces the video game screen data (S4). Here, the video gamescreen data is the image data representing the perspective view of the3D object operable data, the 3D object non-operable data, and the 3Dbackground data retrieved in S2 after being processed in S3, which isdesigned to be displayed on LCD 201 (FIG. 1). CPU 211 stores the videogame screen data in Work Area 206103b3 (Paragraph [0337]), and displaysthe data on LCD 201 (FIG. 1) (S5). The foregoing sequence is repeatedperiodically.

Paragraph [0346]—This Paragraph [0346] illustrate(s) Video GameContinuing Software 206103c2 (Paragraph [0338]) of Communication Device200, which continues and resumes the video game. In the presentembodiment, CPU 211 (FIG. 1) of Communication Device 200 periodicallychecks the game status (S1). If the game is over, CPU 211 proceeds tothe next step (S2). CPU 211 initiates the video game continuing process(S3). If the video game continuing signal is input during video gamecontinuing process, CPU 211 proceeds to the next step (S4). Here, thevideo game continuing signal is a signal input by utilizing Input Device210 (FIG. 1) or via voice recognition system indicating to initiate thevideo game resuming process described in the next step. CPU 211initiates the video game resuming process (S5). Here, the video game iscontinued and resumed from the point where the game ended. As anotherembodiment, if the video game includes a plurality of game stages, andthe game ended at a middle of a certain game stage, the video game iscontinued and resumed from the beginning of the game stage where thegame ended.

Paragraph [0347]—This Paragraph [0347] illustrate(s) the video gamecontinuing process described in the previous embodiment. In the presentembodiment, CPU 211 (FIG. 1) of Communication Device 200 retrieves thecount down image data (e.g., Count Down Image ‘10’ Data) from Count DownData Storage Area 206103b2 (Paragraph [0337]) (S1). CPU 211 produces thevideo game screen data (S2). CPU 211 stores the video game screen datain Work Area 206103b3 (Paragraph [0337]), and displays the data on LCD201 (FIG. 1) (S3). The foregoing sequence is repeated periodically.Thus, the count down image ‘10’ data is displayed on LCD 201 (FIG. 1)for a certain period of time, the count down image ‘9’ data is displayedon LCD 201 (FIG. 1) for a certain period of time, the count down image‘8’ data is displayed on LCD 201 (FIG. 1) for a certain period of time,the count down image ‘7’ data is displayed on LCD 201 (FIG. 1) for acertain period of time, the count down image ‘6’ data is displayed onLCD 201 (FIG. 1) for a certain period of time, the count down image ‘5’data is displayed on LCD 201 (FIG. 1) for a certain period of time, thecount down image ‘4’ data is displayed on LCD 201 (FIG. 1) for a certainperiod of time, the count down image ‘3’ data is displayed on LCD 201(FIG. 1) for a certain period of time, the count down image ‘2’ data isdisplayed on LCD 201 (FIG. 1) for a certain period of time, and thecount down image ‘1’ data is displayed on LCD 201 (FIG. 1) for a certainperiod of time.

Paragraph [0348]—<<Resume Enabled Video Game Function>>

Paragraph [0349]—Paragraph [0350] through Paragraph [0367] illustrate(s)the resume enabled video game function which enables a video game to beresumed from the point at which the video game ended last time. Forexample, the user of Communication Device 200 may end playing the videogame and close the video game software, and open the software on thenext day and resume from the point he/she ended last day.

Paragraph [0350]—This Paragraph [0350] illustrate(s) the storage areaincluded in Host H (Paragraph [0022]). In the present embodiment, Host Hincludes Resume Enabled Video Game Information Storage Area H104a ofwhich the data and the software programs stored therein are described inParagraph [0351].

Paragraph [0351]—This Paragraph [0351] illustrate(s) the storage areasincluded in Resume Enabled Video Game Information Storage Area H104a(Paragraph [0350]). In the present embodiment, Resume Enabled Video GameInformation Storage Area H104a includes Resume Enabled Video Game DataStorage Area H104b and Resume Enabled Video Game Software Storage AreaH104c. Resume Enabled Video Game Data Storage Area H104b stores the datanecessary to implement the present function on the side of Host H(Paragraph [0022]), such as the ones described in Paragraph [0352].Resume Enabled Video Game Software Storage Area H104c stores thesoftware programs necessary to implement the present function on theside of Host H, such as the ones described in Paragraph [0353].

Paragraph [0352]—This Paragraph [0352] illustrate(s) the storage areasincluded in Resume Enabled Video Game Data Storage Area H104b (Paragraph[0351]). In the present embodiment, Resume Enabled Video Game DataStorage Area H104b includes 3D Object Data Storage Area H104b1,Middleway Resuming Data Storage Area H104b2, and Work Area H104b3. 3DObject Data Storage Area H104b1 stores the 3D object operable data, the3D object non-operable data, and the 3D background data. Here, the 3Dobject operable data represents the 3D object displayed on LCD 201(FIG. 1) which is capable to be manipulated by the user of CommunicationDevice 200. The 3D object non-operable data represents the 3D objectdisplayed on LCD 201 (FIG. 1) which is not capable to be manipulated bythe user of Communication Device 200. The 3D background data representsthe 3D object which is displayed on LCD 201 (FIG. 1) as a background(e.g., sky, clouds, buildings, and streets) of the corresponding videogame. Middleway Resuming Data Storage Area H104b2 stores the middlewayresuming data. Here, the middleway resuming data represents the point atwhich the video game ended last time. The middleway resuming data isutilized when the video game software program is executed next time andthe user of Communication Device 200 desires to resume the video gamefrom the point at which the video game ended last time. Work Area H104b3is utilized as a work area to perform calculation and temporarily storedata.

Paragraph [0353]—This Paragraph [0353] illustrate(s) the softwareprograms stored in Resume Enabled Video Game Software Storage Area H104c(Paragraph [0351]). In the present embodiment, Resume Enabled Video GameSoftware Storage Area H104c stores Video Game Processing SoftwareH104c1, Video Game Middleway Ending Software H104c2, Video GameMiddleway Resuming Software H104c3, and Video Game Downloading SoftwareH104c4. Video Game Processing Software H104c1 is the software programdescribed in Paragraph [0359]. Video Game Middleway Ending SoftwareH104c2 is the software program described in Paragraph [0360]. Video GameMiddleway Resuming Software H104c3 is the software program described inParagraph [0361]. Video Game Downloading Software H104c4 is the softwareprogram described in Paragraph [0364].

Paragraph [0354]—This Paragraph [0354] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Communication Device 200. In the presentembodiment, RAM 206 includes Resume Enabled Video Game InformationStorage Area 206104a of which the data and the software programs storedtherein are described in Paragraph [0356].

Paragraph [0355]—The data and/or the software programs stored in ResumeEnabled Video Game Information Storage Area 206104a (Paragraph [0354])may be downloaded from Host H (Paragraph [0022]) in the manner describedin Paragraph [0416] through Paragraph [0422].

Paragraph [0356]—This Paragraph [0356] illustrate(s) the storage areasincluded in Resume Enabled Video Game Information Storage Area 206104a(Paragraph [0354]). In the present embodiment, Resume Enabled Video GameInformation Storage Area 206104a includes Resume Enabled Video Game DataStorage Area 206104b and Resume Enabled Video Game Software Storage Area206104c. Resume Enabled Video Game Data Storage Area 206104b stores thedata necessary to implement the present function on the side ofCommunication Device 200, such as the ones described in Paragraph[0357]. Resume Enabled Video Game Software Storage Area 206104c storesthe software programs necessary to implement the present function on theside of Communication Device 200, such as the ones described inParagraph [0358].

Paragraph [0357]—This Paragraph [0357] illustrate(s) the storage areasincluded in Resume Enabled Video Game Data Storage Area 206104b(Paragraph [0356]). In the present embodiment, Resume Enabled Video GameData Storage Area 206104b includes 3D Object Data Storage Area 206104b1,Middleway Resuming Data Storage Area 206104b2, and Work Area 206104b3.3D Object Data Storage Area 206104b1 stores the 3D object operable data,the 3D object non-operable data, and the 3D background data. Here, the3D object operable data represents the 3D object displayed on LCD 201(FIG. 1) which is capable to be manipulated by the user of CommunicationDevice 200. The 3D object non-operable data represents the 3D objectdisplayed on LCD 201 (FIG. 1) which is not capable to be manipulated bythe user of Communication Device 200. The 3D background data representsthe 3D object which is displayed on LCD 201 (FIG. 1) as a background(e.g., sky, clouds, buildings, and streets) of the corresponding videogame. Middleway Resuming Data Storage Area 206104b2 stores the middlewayresuming data. Here, the middleway resuming data represents the point atwhich the video game ended last time. The middleway resuming data isutilized when the video game software program is executed next time andthe user of Communication Device 200 desires to resume the video gamefrom the point at which the video game ended last time. Work Area206104b3 is utilized as a work area to perform calculation andtemporarily store data.

Paragraph [0358]—This Paragraph [0358] illustrate(s) the softwareprograms stored in Resume Enabled Video Game Software Storage Area206104c (Paragraph [0356]). In the present embodiment, Resume EnabledVideo Game Software Storage Area 206104c stores Video Game ProcessingSoftware 206104c1, Video Game Middleway Ending Software 206104c2, VideoGame Middleway Resuming Software 206104c3, and Video Game DownloadingSoftware 206104c4. Video Game Processing Software 206104c1 is thesoftware program described in Paragraph [0359] and Paragraph [0365].Video Game Middleway Ending Software 206104c2 is the software programdescribed in Paragraph [0360] and Paragraph [0366]. Video Game MiddlewayResuming Software 206104c3 is the software program described inParagraph [0361] and Paragraph [0367]. Video Game Downloading Software206104c4 is the software program described in Paragraph [0364].

Paragraph [0359]—This Paragraph [0359] illustrate(s) Video GameProcessing Software H104c1 (Paragraph [0353]) of Host H (Paragraph[0022]) and Video Game Processing Software 206104c1 (Paragraph [0358])of Communication Device 200, which process the video game. In thepresent embodiment, CPU 211 (FIG. 1) of Communication Device 200 sendsthe video game command signal, which is received by Host H (S1). Here,the video game command signal is a signal input by utilizing InputDevice 210 (FIG. 1) or via voice recognition system to operate the 3Dobject operable data displayed on LCD 201 (FIG. 1). Host H retrieves the3D object operable data, the 3D object non-operable data, and the 3Dbackground data from 3D Object Data Storage Area H104b1 (Paragraph[0352]) (S2). Host H processes with the data retrieved in the previousstep in accordance with the video command signal received in S1 (S3).Host H produces the video game screen data, which is sent toCommunication Device 200 (S4). Here, the video game screen data is theimage data representing the perspective view of the 3D object operabledata, the 3D object non-operable data, and the 3D background dataretrieved in S2 after being processed in S3, which is designed to bedisplayed on LCD 201 (FIG. 1). CPU 211 receives the video game screendata and stores the data in Work Area 206104b3 (Paragraph [0357]) anddisplays the data on LCD 201 (FIG. 1) (S5). The foregoing sequence isrepeated periodically.

Paragraph [0360]—This Paragraph [0360] illustrate(s) Video GameMiddleway Ending Software H104c2 (Paragraph [0353]) of Host H (Paragraph[0022]) and Video Game Middleway Ending Software 206104c2 (Paragraph[0358]) of Communication Device 200, which end the video game. In thepresent embodiment, the user of Communication Device 200 inputs thevideo game middleway ending signal which is sent to Host H (S1). Here,the video game middleway ending signal is a signal input by utilizingInput Device 210 (FIG. 1) or via voice recognition system indicating toend the video game and record the point at which the video game endedfor purposes from which the video game to be resumed when the video gamesoftware is executed next time. Host H receives the video game middlewayending signal (S2). Host H, in response, produces the middleway resumingdata and stores the data in Middleway Resuming Data Storage Area H104b2(Paragraph [0352]) (S3). Host H ends the video game thereafter (S4).

Paragraph [0361]—This Paragraph [0361] illustrate(s) Video GameMiddleway Resuming Software H104c3 (Paragraph [0353]) of Host H(Paragraph [0022]) and Video Game Middleway Resuming Software 206104c3(Paragraph [0358]) of Communication Device 200, which resume the videogame. In the present embodiment, the user of Communication Device 200inputs the video game middleway resuming signal which is sent to Host H(S1). Here, the video game middleway resuming signal is a signal inputby utilizing Input Device 210 (FIG. 1) or via voice recognition systemindicating to resume the video game from the point at which the videogame ended last time. Host H receives the video game middleway resumingsignal (S2). Host H retrieves the middleway resuming data from MiddlewayResuming Data Storage Area H104b2 (Paragraph [0352]) (S3). Host Hresumes the video game in accordance with the middleway resuming dataretrieved in the previous step (S4). Video Game Processing SoftwareH104c1 of Host H and Video Game Processing Software 206104c1 ofCommunication Device 200 are executed and the video game is resumed fromthe point at which the video game ended last time. As anotherembodiment, if the video game includes a plurality of game stages, andthe video game ended at a middle of a certain game stage, the video gamemay be continued and resumed from the beginning of the video game stagewhere the video game ended last time.

Paragraph [0362]—<<Resume Enabled Video Game Function—AnotherEmbodiment>>

Paragraph [0363]—Paragraph [0364] through Paragraph [0367] illustrate(s)another embodiment, wherein the present function is implemented solelyby Communication Device 200. Paragraph [0364]—This Paragraph [0364]illustrate(s) Video Game Downloading Software H104c4 (Paragraph [0353])of Host H (Paragraph [0022]) and Video Game Downloading Software206104c4 (Paragraph [0358]) of Communication Device 200, which enableCommunication Device 200 to download a video game software capable toimplement the present function. In the present embodiment, Host Hretrieves all data from Resume Enabled Video Game Information StorageArea H104a (Paragraph [0350]), which is sent to Communication Device 200(S1). CPU 211 (FIG. 1) of Communication Device 200 receives the dataretrieved in the previous step and stores the data in Resume EnabledVideo Game Information Storage Area 206104a (Paragraph [0354]) (S2).

Paragraph [0365]—This Paragraph [0365] illustrate(s) Video GameProcessing Software 206104c1 (Paragraph [0358]) of Communication Device200, which processes the video game. In the present embodiment, the userof Communication Device 200 inputs the video game command signal (S1).Here, the video game command signal is a signal input by utilizing InputDevice 210 (FIG. 1) or via voice recognition system to operate the 3Dobject operable data displayed on LCD 201 (FIG. 1). CPU 211 retrievesthe 3D object operable data, the 3D object non-operable data, and the 3Dbackground data from 3D Object Data Storage Area 206104b1 (Paragraph[0357]) (S2). CPU 211 processes with the data retrieved in the previousstep in accordance with the video command signal input in S1 (S3). CPU211 produces the video game screen data (S4). Here, the video gamescreen data is the image data representing the perspective view of the3D object operable data, the 3D object non-operable data, and the 3Dbackground data retrieved in S2 after being processed in S3, which isdesigned to be displayed on LCD 201 (FIG. 1). CPU 211 stores the videogame screen data in Work Area 206104b3 (Paragraph [0357]) and displaysthe data on LCD 201 (FIG. 1) (S5). The foregoing sequence is repeatedperiodically.

Paragraph [0366]—This Paragraph [0366] illustrate(s) Video GameMiddleway Ending Software 206104c2 (Paragraph [0358]) of CommunicationDevice 200, which ends the video game. In the present embodiment, theuser of Communication Device 200 inputs the video game middleway endingsignal (S1). Here, the video game middleway ending signal is a signalinput by utilizing Input Device 210 (FIG. 1) or via voice recognitionsystem indicating to end the video game and record the point at whichthe video game ended for purposes from which the video game to beresumed when the video game software is executed next time. CPU 211, inresponse, produces the middleway resuming data and stores the data inMiddleway Resuming Data Storage Area 206104b2 (Paragraph [0357]) (S2).CPU 211 ends the video game thereafter (S3).

Paragraph [0367]—This Paragraph [0367] illustrate(s) Video GameMiddleway Resuming Software 206104c3 (Paragraph [0358]) of CommunicationDevice 200, which resumes the video game. In the present embodiment, theuser of Communication Device 200 inputs the video game middlewayresuming signal (S1). Here, the video game middleway resuming signal isa signal input by utilizing Input Device 210 (FIG. 1) or via voicerecognition system indicating to resume the video game from the point atwhich the video game ended last time. CPU 211 retrieves the middlewayresuming data from Middleway Resuming Data Storage Area 206104b2(Paragraph [0357]) (S2). CPU 211 resumes the video game in accordancewith the middleway resuming data retrieved in the previous step (S3).Video Game Processing Software 206104c1 of Communication Device 200 isexecuted and the video game is resumed from the point at which the videogame ended last time. As another embodiment, if the video game includesa plurality of game stages, and the video game ended at a middle of acertain game stage, the video game may be continued and resumed from thebeginning of the video game stage where the video game ended last time.

Paragraph [0368]—<<Signal Forwarding Function>>

Paragraph [0369]—Paragraph [0370] through Paragraph [0391] illustrate(s)the signal forwarding function by which a wireless signal received froma wireless communication device is forwarded to another wirelesscommunication device by implementing the present function.

Paragraph [0370]—This Paragraph [0370] illustrate(s) the overalloperation of the present function. Four Communication Devices 200, forexample, Device A, Device B, Device C, and Device D are utilized todescribe the present function. In the present embodiment, Device D isnot within the communication range of Device A. In contrast, Device Band Device C are within the communication range of Device A. Device D iswithin the communication range of Device B and Device C. Device C iswithin the communication range of Device B. In the present example,Device A is capable to communicate with Device D via (Device B and)Device C, i.e., having Device A's wireless signal being forward toDevice D by (Device B and) Device C. The device IDs are utilized toimplement the present function: the device ID of Device A is ‘Device#A’;the device ID of Device B is ‘Device#B’; the device ID of Device C is‘Device#C’; and the device ID of Device D is ‘Device#D’. Here, eachdevice ID is an identification of the corresponding Communication Device200.

Paragraph [0371]—This Paragraph [0371] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Devices A through D. In the presentembodiment, RAM 206 includes Signal Forwarding Information Storage Area206105a of which the data and the software programs stored therein aredescribed in Paragraph [0373].

Paragraph [0372]—The data and/or the software programs stored in SignalForwarding Information Storage Area 206105a (Paragraph [0371]) may bedownloaded from Host H (Paragraph [0022]) in the manner described inParagraph [0416] through Paragraph [0422].

Paragraph [0373]—This Paragraph [0373] illustrate(s) the storage areasincluded in Signal Forwarding Information Storage Area 206105a(Paragraph [0371]). In the present embodiment, Signal ForwardingInformation Storage Area 206105a includes Signal Forwarding Data StorageArea 206105b and Signal Forwarding Software Storage Area 206105c. SignalForwarding Data Storage Area 206105b stores the data necessary toimplement the present function, such as the ones described in Paragraph[0374]. Signal Forwarding Software Storage Area 206105c stores thesoftware programs necessary to implement the present function, such asthe ones described in Paragraph [0375].

Paragraph [0374]—This Paragraph [0374] illustrate(s) the storage areasincluded in Signal Forwarding Data Storage Area 206105b (Paragraph[0373]). In the present embodiment, Signal Forwarding Data Storage Area206105b includes Origin Device ID Storage Area 206105b1, DestinationDevice TD Storage Area 206105b2, Communication Route Data Storage Area206105b3, Communication Data Storage Area 206105b4, and Work Area206105b5. Origin Device ID Storage Area 206105b1 stores the origindevice ID which represents the device ID (e.g., Device#A) ofCommunication Device 200 which transmits a wireless signal. In thepresent example, the device ID ‘Device#A’ is the origin device ID, i.e.,Device A transmits the wireless signal, which is received by Device D byhaving the wireless signal being forwarded by (Device B and) Device C.Destination Device ID Storage Area 206105b2 stores the destinationdevice ID which represents the device ID (e.g., Device#D) ofCommunication Device 200 which receives the wireless signal transmittedby Communication Device 200 of which the device ID is the origin deviceID. In the present example, the device ID ‘Device#D’ is the destinationdevice ID, i.e., Device D receives the wireless signal transmitted byDevice A forwarded by (Device B and) Device C. Communication Route DataStorage Area 206105b3 stores the shortest route from CommunicationDevice 200 represented by the origin device ID (e.g., Device#A) toCommunication Device 200 represented by the destination device ID (e.g.,Device#D). Communication Data Storage Area 206105b4 stores thecommunication data which may include audio data, text data, image data,video data, and/or other types of data. Work Area 206105b5 is utilizedas a work area to perform calculation and temporarily store data.

Paragraph [0375]—This Paragraph [0375] illustrate(s) the softwareprograms stored in Signal Forwarding Software Storage Area 206105c(Paragraph [0373]). In the present embodiment, Signal ForwardingSoftware Storage Area 206105c stores Route Inquiry Initiating Software206105c1, Route Inquiry Signal Forwarding Software 206105c2, RouteInquiry Signal Receiving Software 206105c3, Route Comparing Software206105c4, Route Response Initiating Software 206105c5, Route ResponseSignal Forwarding Software 206105c6, Route Response Signal ReceivingSoftware 206105c7, Origin Device Communicating Software 206105c8,Communication Data Forwarding Software 206105c9, and Communication DataReceiving Software 206105c10. Route Inquiry Initiating Software 206105c1is the software program described in Paragraph [0377]. Route InquirySignal Forwarding Software 206105c2 is the software program described inParagraph [0378] and Paragraph [0379]. Route Inquiry Signal ReceivingSoftware 206105c3 is the software program described in Paragraph [0380].Route Comparing Software 206105c4 is the software program described inParagraph [0388]. Route Response Initiating Software 206105c5 is thesoftware program described in Paragraph [0381]. Route Response SignalForwarding Software 206105c6 is the software program described inParagraph [0382]. Route Response Signal Receiving Software 206105c7 isthe software program described in Paragraph [0383]. Origin DeviceCommunicating Software 206105c8 is the software program described inParagraph [0389]. Communication Data Forwarding Software 206105c9 is thesoftware program described in Paragraph [0390]. Communication DataReceiving Software 206105c10 is the software program described inParagraph [0391].

Paragraph [0376]—This Paragraph [0376] illustrate(s) the data includedin the route inquiry signal which is utilized to implement the presentfunction. In the present embodiment, the route inquire signal includesthe origin device ID, the forwarding device IDs, and the destinationdevice ID. Here, the origin device ID represents the device ID (e.g.,Device#A) of Communication Device 200 which transmits a wireless signal.The destination device ID represents the device ID (e.g., Device#D) ofCommunication Device 200 which receives the wireless signal transmittedby Communication Device 200 of which the device ID is the origin deviceID (e.g., Device#A). The forwarding device IDs represent the device IDs(e.g., Device#C and Device#D) of Communication Devices 200 which forwardthe wireless signal received from Communication Device 200 of which thedevice ID is the origin device ID (e.g., Device#A) to CommunicationDevice 200 of which the device ID is the destination device ID (e.g.,Device#D).

Paragraph [0377]—This Paragraph [0377] illustrate(s) Route InquiryInitiating Software 206105c1 (Paragraph [0375]) of Device A, whichinitiates to transfer the route inquiry signal. In the presentembodiment, CPU 211 (FIG. 1) of Device A produces the route inquirysignal (S1). CPU 211 retrieves the origin device ID (e.g., Device#A)from Origin Device ID Storage Area 206105b1 and adds the data to theroute inquiry signal (S2). CPU 211 retrieves the destination device ID(e.g., Device#D) from Destination Device ID Storage Area 206105b2 andadds the data to the route inquiry signal (S3). CPU 211 sends the routeinquiry signal in a wireless fashion via Antenna 218 (FIG. 1) toCommunication Device 200 within its communication range (e.g., Devices Band C) (S4).

Paragraph [0378]—This Paragraph [0378] illustrate(s) Route InquirySignal Forwarding Software 206105c2 (Paragraph [0375]) of Device B,which forwards the route inquiry signal. In the present embodiment, CPU211 (FIG. 1) of Device B receives signal via Antenna 218 (FIG. 1) (S1).If the signal received in S1 is the route inquiry signal, CPU 211proceeds to the next step (S2). If own device ID (e.g., Device#B) is NOTincluded in the destination device ID of the route inquiry signal, CPU211 proceeds to the next step (S3). CPU 211 adds its own device ID(e.g., Device#B) as the forwarding device ID to the route inquiry signaland sends via Antenna 218 (FIG. 1) the data to Communication Device 200located within its communication range (e.g., Device C) (S4). Theforegoing sequence is performed periodically.

Paragraph [0379]—This Paragraph [0379] illustrate(s) Route InquirySignal Forwarding Software 206105c2 (Paragraph [0375]) of Device C,which forwards the route inquiry signal. In the present embodiment, CPU211 (FIG. 1) of Device C receives signal via Antenna 218 (FIG. 1) (S1).If the signal received in S1 is the route inquiry signal, CPU 211proceeds to the next step (S2). If own device ID (e.g., Device#C) is NOTincluded in the destination device ID of the route inquiry signal, CPU211 proceeds to the next step (S3). CPU 211 adds its own device ID(e.g., Device#C) as the forwarding device ID to the route inquiry signaland sends via Antenna 218 (FIG. 1) the data to Communication Device 200located within its communication range (e.g., Device C) (S4). Theforegoing sequence is performed periodically.

Paragraph [0380]—This Paragraph [0380] illustrate(s) Route InquirySignal Receiving Software 206105c3 (Paragraph [0375]) of Device D, whichreceives the route inquiry signal. In the present embodiment, CPU 211(FIG. 1) of Device D receives signal via Antenna 218 (FIG. 1) (S1). Ifthe signal received in S1 is the route inquiry signal, CPU 211 proceedsto the next step (S2). If own device ID (e.g., Device#D) is included inthe destination device ID of the route inquiry signal, CPU 211 proceedsto the next step (S3). CPU 211 stores the route inquiry signal in WorkArea 206105c (S4). The foregoing sequence is performed periodically.

Paragraph [0381]—This Paragraph [0381] illustrate(s) Route ResponseInitiating Software 206105c5 (Paragraph [0375]) of Device D, which sendsa response to the route inquiry signal. In the present embodiment, CPU211 (FIG. 1) of Device D retrieves the route inquiry signal from WorkArea 206105c and produces the route response signal and includes theroute inquiry signal therein (S1). CPU 211 returns the route responsesignal via Antenna 218 (FIG. 1) to the previous Communication Device 200(e.g., Device C) by referring to the route inquiry signal included inthe route response signal (S2).

Paragraph [0382]—This Paragraph [0382] illustrate(s) Route ResponseSignal Forwarding Software 206105c6 (Paragraph [0375]) of Devices C andB, which forward the route response signal. Taking Device C for example,CPU 211 (FIG. 1) of Device C receives signal via Antenna 218 (FIG. 1)(S1). If the signal received in S1 is the route response signal, CPU 211proceeds to the next step (S2). CPU 211 returns the route responsesignal via Antenna 218 (FIG. 1) to the previous Communication Device 200(e.g., Device A) by referring to the route inquiry signal included inthe route response signal (S3). The foregoing sequence is performedperiodically.

Paragraph [0383]—This Paragraph [0383] illustrate(s) Route ResponseSignal Receiving Software 206105c7 (Paragraph [0375]) of Device A, whichreceives the route response signal. In the present embodiment, CPU 211(FIG. 1) of Device A receives signal via Antenna 218 (FIG. 1) (S1). Ifthe signal received in S1 is the route response signal, CPU 211 proceedsto the next step (S2). CPU 211 stores the route response signal in WorkArea 206105c (S3). The foregoing sequence is performed periodically.

Paragraph [0384]—This Paragraph [0384] illustrate(s) the overall processdescribed in the previous seven software programs. In the presentembodiment, CPU 211 (FIG. 1) of Device A retrieves the destinationdevice ID (e.g., Device#D) from Destination Device ID Storage Area206105b2 and adds the data to the route inquiry signal (S1). CPU 211 ofDevice A adds its own device ID (e.g., Device#A) to the route inquirysignal and sends the route inquiry signal (S2). CPU 211 (FIG. 1) ofDevice B receives the route inquiry signal and adds its own device ID(e.g., Device#B) to the route inquiry signal and sends the route inquirysignal (S3). CPU 211 (FIG. 1) of Device C receives the route inquirysignal and adds its own device ID (e.g., Device#C) to the route inquirysignal and sends the route inquiry signal (S4). CPU 211 (FIG. 1) ofDevice D receives the route inquiry signal and adds its own device ID(e.g., Device#D) to the route inquiry signal (S5).

Paragraph [0385]—This Paragraph [0385] illustrate(s) the simplifieddescription of the process described in the previous embodiment. In thepresent embodiment, the route inquiry signal is transferred from DeviceA which is forward by Device B and Device C, and received by Device D.

Paragraph [0386]—This Paragraph [0386] illustrate(s) the overall processof the software programs described hereinbefore. In the presentembodiment, CPU 211 (FIG. 1) of Device A retrieves the destinationdevice ID (e.g., Device#D) from Destination Device ID Storage Area206105b2 and adds the data to the route inquiry signal (S1). CPU 211 ofDevice A adds its own device ID (e.g., Device#A) to the route inquirysignal and sends the route inquiry signal (S2). CPU 211 (FIG. 1) ofDevice C receives the route inquiry signal and adds its own device ID(e.g., Device#C) to the route inquiry signal and sends the route inquirysignal (S3). CPU 211 (FIG. 1) of Device D receives the route inquirysignal and adds its own device ID (e.g., Device#D) to the route inquirysignal (S4).

Paragraph [0387]—This Paragraph [0387] illustrate(s) the simplifieddescription of the process described in the previous embodiment. In thepresent embodiment, the route inquiry signal is transferred from DeviceA to Device C, and received by Device D.

Paragraph [0388]—This Paragraph [0388] illustrate(s) Route ComparingSoftware 206105c4 (Paragraph [0375]) of Device A, which compares theroute inquiry signals to identify the shortest route. In the presentembodiment, CPU 211 (FIG. 1) of Device A retrieves all route responsesignals from Work Area 206105b5 (S1). CPU 211 retrieves the routeinquiry signals from the route response signals (S2). CPU 211 comparesall route inquiry signals (S3). CPU 211 identifies the route inquirysignal representing the shortest route and stores the data as thecommunication route data (e.g., Communication Route Data#A) inCommunication Route Data Storage Area 206105b3 (S4).

Paragraph [0389]—This Paragraph [0389] illustrate(s) Origin DeviceCommunicating Software 206105c8 (Paragraph [0375]) of Device A, whichsends the communication data. In the present embodiment, CPU 211(FIG. 1) of Device A retrieves the communication route data (e.g.,Communication Route Data#A) from Communication Route Data Storage Area206105b3 (S1). CPU 211 retrieves the communication data fromCommunication Data Storage Area 206105b4 (S2). Here, the communicationdata may include audio data, text data, image data, video data, and/orother types of data. CPU 211 produces the device to device communicatingsignal and adds its data retrieved in S1 and S2 (S3). Here, the deviceto device communicating signal is a signal produced for purposes ofcommunicating (sending/receiving audio data, text data, image data,video data, and/or other types of data) with Communication Device 200(e.g., Device D) of which the device ID (e.g., Device#D) is thedestination device ID. CPU 211 sends the device to device communicatingsignal in accordance with the communication route data (e.g.,Communication Route Data#A) (e.g., to Device C) via Antenna 218 (FIG. 1)(S4).

Paragraph [0390]—This Paragraph [0390] illustrate(s) Communication DataForwarding Software 206105c9 (Paragraph [0375]) of Device C, whichforwards the communication data. In the present embodiment, CPU 211(FIG. 1) of Device C receives signal via Antenna 218 (FIG. 1) (S1). Ifthe signal received in S1 is the device to device communicating signal,CPU 211 proceeds to the next step (S2). If own device ID (e.g.,Device#C) is NOT included in destination device ID of the device todevice communicating signal, CPU 211 proceeds to the next step (S3). CPU211 forwards the device to device communicating signal in accordancewith the communication route data (e.g., Communication Route Data#A)(e.g., to Device D) via Antenna 218 (FIG. 1) (S4). The foregoingsequence is performed periodically.

Paragraph [0391]—This Paragraph [0391] illustrate(s) Communication DataReceiving Software 206105c10 (Paragraph [0375]) of Device D, whichreceives the communication data. In the present embodiment, CPU 211(FIG. 1) of Device D receives signal via Antenna 218 (FIG. 1) (S1). Ifthe signal received in S1 is the device to device communicating signal,CPU 211 proceeds to the next step (S2). If own device ID (e.g.,Device#D) is included in destination device ID of the device to devicecommunicating signal, CPU 211 proceeds to the next step (S3). CPU 211stores the device to device communicating signal in Work Area 206105b5(S4). CPU 211 retrieves the communication data from the device to devicecommunicating signal (S5). CPU 211 processes with the communication datathereafter (S6). The foregoing sequence is performed periodically.

Paragraph [0392]—<<Voice Message Displaying Function>>

Paragraph [0393]—Paragraph [0394] through Paragraph [0405] illustrate(s)the voice message displaying function which converts the message data, avoice data, stored by implementing the answering machine mode into textdata.

Paragraph [0394]—This Paragraph [0394] illustrate(s) the storage areaincluded in RAM 206 (FIG. 1) of Communication Device 200. In the presentembodiment, RAM 206 includes Voice Message Displaying InformationStorage Area 206107a of which the data and the software programs storedtherein are described in Paragraph [0396].

Paragraph [0395]—The data and/or the software programs stored in VoiceMessage Displaying Information Storage Area 206107a (Paragraph [0394])may be downloaded from Host H (Paragraph [0022]) in the manner describedin Paragraph [0416] through Paragraph [0422].

Paragraph [0396]—This Paragraph [0396] illustrate(s) the storage areasincluded in Voice Message Displaying Information Storage Area 206107a(Paragraph [0394]). In the present embodiment, Voice Message DisplayingInformation Storage Area 206107a includes Voice Message Displaying DataStorage Area 206107b and Voice Message Displaying Software Storage Area206107c. Voice Message Displaying Data Storage Area 206107b stores thedata necessary to implement the present function, such as the onesdescribed in Paragraph [0397]. Voice Message Displaying Software StorageArea 206107c stores the software programs necessary to implement thepresent function, such as the ones described in Paragraph [0401].

Paragraph [0397]—This Paragraph [0397] illustrate(s) the storage areasincluded in Voice Message Displaying Data Storage Area 206107b(Paragraph [0396]). In the present embodiment, Voice Message DisplayingData Storage Area 206107b includes Answering Machine Message DataStorage Area 206107b1, Caller's Message Data Storage Area 206107b2, TimeStamp Data Storage Area 206107b3, Text Message Data Storage Area206107b4, and Work Area 206107b5. Answering Machine Message Data StorageArea 206107b1 stores the answering machine message data which is thevoice data indicating that the user of Communication Device 200 (callee)can not answer the call and also indicating to leave a message. Caller'sMessage Data Storage Area 206107b2 stores the data described inParagraph [0398]. Time Stamp Data Storage Area 206107b3 stores the datadescribed in Paragraph [0399]. Text Message Data Storage Area 206107b4stores the data described in Paragraph [0400]. Work Area 206107b5 isutilized as a work area to perform calculation and temporarily storedata.

Paragraph [0398]—This Paragraph [0398] illustrate(s) the data stored inCaller's Message Data Storage Area 206107b2 (Paragraph [0397]). In thepresent embodiment, Caller's Message Data Storage Area 206107b2comprises two columns, i.e., ‘Message ID’ and ‘Caller's Message Data’.Column ‘Message ID’ stores the message IDs, and each message ID is anidentification of the corresponding caller's message data stored incolumn ‘Caller's Message Data’. Here, the message ID may be the caller'sphone number or his/her name. Column ‘Caller's Message Data’ stores thecaller's message data, and each caller's message data is the voice dataof the caller who called the user of Communication Device 200. In thepresent embodiment, Caller's Message Data Storage Area 206107b2 storesthe following data: the message ID ‘Message#1’ and the correspondingcaller's message data ‘Caller's Message Data#1’; the message ID‘Message#2’ and the corresponding caller's message data ‘Caller'sMessage Data#2’; the message ID ‘Message#3’ and the correspondingcaller's message data ‘Caller's Message Data#3’; and the message ID‘Message#4’ and the corresponding caller's message data ‘Caller'sMessage Data#4’.

Paragraph [0399]—This Paragraph [0399] illustrate(s) the data stored inTime Stamp Data Storage Area 206107b3 (Paragraph [0397]). In the presentembodiment, Time Stamp Data Storage Area 206107b3 comprises two columns,i.e., ‘Message ID’ and ‘Time Stamp Data’. Column ‘Message ID’ stores themessage IDs, and each message ID is an identification of thecorresponding time stamp data stored in column ‘Time Stamp Data’. Themessage IDs stored in Time Stamp Data Storage Area 206107b3 areidentical to the ones stored in Caller's Message Data Storage Area206107b2 (Paragraph [0398]). Column ‘Time Stamp Data’ stores the timestamp data, and each time stamp data is the data indicating the date,day, and time at which the caller's message data of the correspondingmessage ID is stored in Caller's Message Data Storage Area 206107b2(Paragraph [0398]). In the present embodiment, Time Stamp Data StorageArea 206107b3 stores the following data: the message ID ‘Message#1’ andthe corresponding time stamp data ‘Time Stamp Data#1’; the message ID‘Message#2’ and the corresponding time stamp data ‘Time Stamp Data#2’;the message ID ‘Message#3’ and the corresponding time stamp data ‘TimeStamp Data#3’; and the message ID ‘Message#4’ and the corresponding timestamp data ‘Time Stamp Data#4’.

Paragraph [0400]—This Paragraph [0400] illustrate(s) the data stored inText Message Data Storage Area 206107b4 (Paragraph [0397]). In thepresent embodiment, Text Message Data Storage Area 206107b4 comprisestwo columns, i.e., ‘Message ID’ and ‘Text Message Data’. Column ‘MessageID’ stores the message IDs, and each Message ID is an identification ofthe corresponding text message data stored in column ‘Text MessageData’. The message IDs stored in Text Message Data Storage Area 206107b4(Paragraph [0400]) are identical to the ones stored in Caller's MessageData Storage Area 206107b2 (Paragraph [0398]). Column ‘Text MessageData’ stores the text message data, and each text message data is thetext data to which the caller's message data of the correspondingmessage ID stored in Caller's Message Data Storage Area 206107b2(Paragraph [0398]) is converted by utilizing the voice recognitionsystem. In the present embodiment, Text Message Data Storage Area206107b4 stores the following data: the message ID ‘Message#1’ and thecorresponding text message data ‘Text Message Data#1’; the message ID‘Message#2’ and the corresponding text message data ‘Text MessageData#2’; the message ID ‘Message#3’ and the corresponding text messagedata ‘Text Message Data#3’; and the message ID ‘Message#4’ and thecorresponding text message data ‘Text Message Data#4’.

Paragraph [0401]—This Paragraph [0401] illustrate(s) the softwareprograms stored in Voice Message Displaying Software Storage Area206107c (Paragraph [0396]). In the present embodiment, Voice MessageDisplaying Software Storage Area 206107c stores Answering Machine ModeImplementing Software 206107c1, Afterwards Caller's Message DataConverting Software 206107c2, Text Message Data Displaying Software206107c3, and Realtime Caller's Message Data Converting Software206107c4. Answering Machine Mode Implementing Software 206107c1 is thesoftware program described in Paragraph [0402]. Afterwards Caller'sMessage Data Converting Software 206107c2 is the software programdescribed in Paragraph [0403]. Text Message Data Displaying Software206107c3 is the software program described in Paragraph [0404]. RealtimeCaller's Message Data Converting Software 206107c4 is the softwareprogram described in Paragraph [0405].

Paragraph [0402]—This Paragraph [0402] illustrate(s) Answering MachineMode Implementing Software 206107c1 (Paragraph [0401]) of CommunicationDevice 200, which implements the answering machine mode. In the presentembodiment, CPU 211 (FIG. 1) of Communication Device 200 receives signalvia Antenna 218 (FIG. 1) (S1). If the signal received in S1 is the phonecall signal, CPU 211 (FIG. 1) proceeds to the next step (S2). Here, thephone call signal indicates that another person (caller) is calling theuser of Communication Device 200 (callee) for voice communication. CPU211 connects the call (S3). CPU 211 retrieves the answering machinemessage data from Answering Machine Message Data Storage Area 206107b1and outputs the data to the caller (S4). CPU 211 assigns the caller'sphone number (or his/her name) as the new message ID (e.g., Message#4)(S5). CPU 211 stores the caller's message data at the message ID (e.g.,Message#4) assigned in the previous step in Caller's Message DataStorage Area 206107b2 (Paragraph [0398]) (S6). CPU 211 (FIG. 1) storesthe current time as the time stamp data at the message ID (e.g.,Message#4) assigned in the previous step in Time Stamp Data Storage Area206107b3 (Paragraph [0399]) (S7). CPU 211 disconnects the callthereafter (S8). The foregoing sequence is performed periodically.

Paragraph [0403]—This Paragraph [0403] illustrate(s) Afterwards Caller'sMessage Data Converting Software 206107c2 (Paragraph [0401]) ofCommunication Device 200, which selects a caller's message data andconverts the data to a text message data. In the present embodiment, CPU211 (FIG. 1) of Communication Device 200 retrieves all message IDs fromCaller's Message Data Storage Area 206107b2 (Paragraph [0398]) anddisplays the data on LCD 201 (FIG. 1) (S1). The user of CommunicationDevice 200 selects by utilizing Input Device 210 (FIG. 1) or via voicerecognition system a message ID (e.g., Message#1) (S2). CPU 211 outputsthe corresponding caller's message data (e.g., Caller's Message Data#1)from Speaker 216 (FIG. 1) (S3). CPU 211 retrieves the corresponding timestamp data (e.g., Time Stamp Data#1) from Time Stamp Data Storage Area206107b3 (Paragraph [0399]) and displays the data on LCD 201 (FIG. 1)(S4). If a convert to text message data signal is input by utilizingInput Device 210 (FIG. 1) or via voice recognition system, CPU 211(FIG. 1) proceeds to the next step (S5). Here, the convert to textmessage data signal is a signal to convert the caller's message data(e.g., Message#1) selected in S2 to the text message data (e.g., TextMessage Data#1). CPU 211 converts the caller's message data (e.g.,Caller's Message Data#1) of the message ID (e.g., Message#1) selected inS2 to the text message data (e.g., Text Message Data#1) and displays thedata on LCD 201 (FIG. 1) (S6). CPU 211 stores the text message data(e.g., Text Message Data#1) converted in the previous step at thecorresponding message ID (e.g., Message#1) in Text Message Data StorageArea 206107b4 (Paragraph [0400]) (S7).

Paragraph [0404]—This Paragraph [0404] illustrate(s) Text Message DataDisplaying Software 206107c3 (Paragraph [0401]) of Communication Device200, which displays the text message data on LCD 201 (FIG. 1). In thepresent embodiment, CPU 211 (FIG. 1) of Communication Device 200retrieves all message IDs from Text Message Data Storage Area 206107b4(Paragraph [0400]) (S1). CPU 211 retrieves all corresponding time stampdata from Time Stamp Data Storage Area 206107b3 (Paragraph [0399]) (S2).CPU 211 retrieves all corresponding text message data (however, thefirst portion of each text message data (e.g., first 10 words of eachtext message data)) from Text Message Data Storage Area 206107b4(Paragraph [0400]) (S3). CPU 211 displays the data retrieved in theprevious three steps on LCD 201 (FIG. 1) (S4). The user of CommunicationDevice 200 selects by utilizing Input Device 210 (FIG. 1) or via voicerecognition system a message ID (e.g., Message#1) (S5). CPU 211retrieves the corresponding text message data (the entire data of TextMessage Data#1) and the corresponding message ID (e.g., Message#1) fromText Message Data Storage Area 206107b4 (Paragraph [0400]) (S6). CPU 211retrieves the corresponding time stamp data (e.g., Time Stamp Data#1)from Time Stamp Data Storage Area 206107b3 (Paragraph [0399]) (S7). CPU211 displays the data retrieved in the previous two steps on LCD 201(FIG. 1) (S8).

Paragraph [0405]—This Paragraph [0405] illustrate(s) Realtime Caller'sMessage Data Converting Software 206107c4 (Paragraph [0401]) ofCommunication Device 200, which converts the caller's message data totext message data realtime. In the present embodiment, CPU 211 (FIG. 1)of Communication Device 200 receives signal via Antenna 218 (FIG. 1)(S1). If the signal received in S1 is the phone call signal, CPU 211(FIG. 1) proceeds to the next step (S2). Here, the phone call signalindicates that another person (caller) is calling the user ofCommunication Device 200 (callee) for voice communication. CPU 211connects the call (S3). CPU 211 retrieves the answering machine messagedata from Answering Machine Message Data Storage Area 206107b1 andoutputs the data to the caller (S4). CPU 211 assigns the caller's phonenumber (or his/her name) as the new message ID (e.g., Message#4) (S5).CPU 211 stores the caller's message data (e.g., Caller's Message Data#4)at the message ID (e.g., Message#4) assigned in the previous step inCaller's Message Data Storage Area 206107b2 (Paragraph [0398]) (S6). CPU211 stores the current time as the time stamp data (e.g., Time StampData#4) at the message ID (e.g., Message#4) assigned in the previousstep in Time Stamp Data Storage Area 206107b3 (Paragraph [0399]) (S7).CPU 211 outputs the caller's message data (e.g., Caller's MessageData#4) stored in S6 from Speaker 216 (FIG. 1) (S8). CPU 211 convertsthe caller's message data (e.g., Caller's Message Data#4) stored in S6to the text message data (e.g., Text Message Data#4) (S9). CPU 211stores the text message data (e.g., Text Message Data#4) converted inthe previous step at the corresponding message ID (e.g., Message#4) inText Message Data Storage Area 206107b4 (Paragraph [0400]) (S10). CPU211 retrieves the text message data (e.g., Text Message Data#4) storedin the previous step from Text Message Data Storage Area 206107b4(Paragraph [0400]) (S11). CPU 211 retrieves the time stamp data (e.g.,Time Stamp Data#4) stored in S7 from Time Stamp Data Storage Area206107b3 (Paragraph [0399]) (S12). CPU 211 displays the data retrievedin the previous two steps on LCD 201 (FIG. 1) (S13). CPU 211 disconnectsthe call thereafter (S14). The foregoing sequence is performedperiodically. The data stored in the foregoing sequence may be displayedon LCD 201 by executing Text Message Data Displaying Software 206107c3(Paragraph [0404]).

Paragraph [0406]—<<Multiple Mode Implementing Function>>

Paragraph [0407]—Paragraph [0408] through Paragraph [0413] illustrate(s)the multiple mode implementing function of Communication Device 200which enables to activate and implement a plurality of modes, functions,and/or systems described in this specification simultaneously.

Paragraph [0408]—This Paragraph [0408] illustrate(s) the softwareprograms stored in RAM 206 (FIG. 1) to implement the multiple modeimplementing function (FIG. 1). As described in Paragraph [0408], RAM206 includes Multiple Mode Implementer Storage Area 20690a. MultipleMode Implementer Storage Area 20690a stores Multiple Mode Implementer20690b, Mode List Displaying Software 20690c, Mode Selecting Software20690d, Mode Activating Software 20690e, and Mode ImplementationRepeater 20690f, all of which are software programs. Multiple ModeImplementer 20690b administers the overall implementation of the presentfunction. One of the major tasks of Multiple Mode Implementer 20690b isto administer and control the timing and sequence of Mode ListDisplaying Software 20690c, Mode Selecting Software 20690d, ModeActivating Software 20690e, and Mode Implementation Repeater 20690f. Forexample, Multiple Mode Implementer 20690b executes them in the followingorder: Mode List Displaying Software 20690c, Mode Selecting Software20690d, Mode Activating Software 20690e, and Mode ImplementationRepeater 20690f. Mode List Displaying Software 20690c displays on LCD201 (FIG. 1) a list of a certain amount or all modes, functions, and/orsystems explained in this specification of which the sequence isexplained in Paragraph [0409]. Mode Selecting Software 20690d selects acertain amount or all modes, functions, and/or systems explained in thisspecification of which the sequence is explained in Paragraph [0410].Mode Activating Software 20690c activates a certain amount or all modes,functions, and/or systems selected by the Mode Selecting Software 20690dof which the sequence is explained in Paragraph [0411]. ModeImplementation Repeater 20690f executes Multiple Mode Implementer 20690bwhich reactivates Mode List Displaying Software 20690c, Mode SelectingSoftware 20690d, Mode Activating Software 20690e of which the sequenceis explained in Paragraph [0412].

Paragraph [0409]—This Paragraph [0409] illustrate(s) the sequence ofMode List Displaying Software 20690c (Paragraph [0408]). Referring toParagraph [0409], CPU 211 (FIG. 1), under the command of Mode ListDisplaying Software 20690c, displays a list of a certain amount or allmodes, functions, and/or systems described in this specification on LCD201 (FIG. 1).

Paragraph [0410]—This Paragraph [0410] illustrate(s) the sequence ofMode Selecting Software 20690d (Paragraph [0408]). Referring toParagraph [0410], the user of Communication Device 200 inputs an inputsignal by utilizing Input Device 210 (FIG. 1) or via voice recognitionsystem identifying one of the modes, functions, and/or systems displayedon LCD 201 (FIG. 1) (S1), and CPU 211 (FIG. 1), under the command ofMode Selecting Software 20690d, interprets the input signal and selectsthe corresponding mode, function, or system (S2).

Paragraph [0411]—This Paragraph [0411] illustrate(s) the sequence ofMode Activating Software 20690e (Paragraph [0408]). Referring toParagraph [0411], CPU 211 (FIG. 1), under the command of Mode ActivatingSoftware 20690e, activates the mode, function, or, system selected in S2of Paragraph [0410]. CPU 211 thereafter implements the activated mode,function, or system as described in the relevant embodiments in thisspecification.

Paragraph [0412]—This Paragraph [0412] illustrate(s) the sequence ofMode Implementation Repeater 20690f (Paragraph [0408]). Referring toParagraph [0412], the user of Communication Device 200 inputs an inputsignal by utilizing Input Device 210 (FIG. 1) or via voice recognitionsystem (S1). Once the activation of the selected mode, function, orsystem described in Paragraph [0411] hereinbefore is completed, and ifthe input signal indicates to repeat the process to activate anothermode, function, or system (S2), CPU 211 (FIG. 1), under the command ofMode Implementation Repeater 20690f, executes Multiple Mode Implementer20690b (Paragraph [0408]), which reactivates Mode List DisplayingSoftware 20690c (Paragraph [0408]), Mode Selecting Software 20690d(Paragraph [0408]), and Mode Activating Software 20690e (Paragraph[0408]) to activate the second mode, function, or system while the firstmode, function, or system is implemented by utilizing the method ofso-called ‘time sharing’ (S3). Mode List Displaying Software 20690c,Mode Selecting Software 20690d, and Mode Activating Software 20690e canbe repeatedly executed until all modes, function, and systems displayedon LCD 201 (FIG. 1) are selected and activated. The activation of modes,functions, and/or systems is not repeated if the input signal explainedin S2 so indicates.

Paragraph [0413]—As another embodiment, Multiple Mode Implementer20690b, Mode List Displaying Software 20690c, Mode Selecting Software20690d, Mode Activating Software 20690e, and Mode ImplementationRepeater 20690f described in Paragraph [0408] may be integrated into onesoftware program, Multiple Mode Implementer 20690b, as described in thisParagraph [0413]. Referring to this Paragraph [0413], CPU 211 (FIG. 1),first of all, displays a list of a certain amount or all modes,functions, and/or systems described in this specification on LCD 201(FIG. 1) (S1). Next, the user of Communication Device 200 inputs aninput signal by utilizing Input Device 210 (FIG. 1) or via voicerecognition system identifying one of the modes, functions, and/orsystems displayed on LCD 201 (S2), and CPU 211 interprets the inputsignal and selects the corresponding mode, function, or system (S3). CPU211 activates the mode, function, or system selected in S3, andthereafter implements the activated mode, function, or system asdescribed in the relevant embodiments in this specification (S4). Oncethe activation of the selected mode, function, or system described in S4is completed, the user of Communication Device 200 inputs an inputsignal by utilizing Input Device 210 or via voice recognition system(S5). If the input signal indicates to repeat the process to activateanother mode, function, or system (S6), CPU 211 repeats the steps S1through S4 to activate the second mode, function, or system while thefirst mode, function, or system is implemented by utilizing the methodso-called ‘time sharing’. The steps of S1 though S4 can be repeatedlyexecuted until all modes, function, and systems displayed on LCD 201 areselected and activated. The activation of modes, functions, and/orsystems is not repeated if the input signal explained in S5 soindicates. As another embodiment, before or at the time one softwareprogram is activated, CPU 211 may, either automatically or manually(i.e., by a signal input by the user of Communication Device), terminatethe other software programs already activated or prohibit other softwareprograms to be activated while one software program is implemented inorder to save the limited space of RAM 206, thereby allowing only onesoftware program implemented at a time. For the avoidance of doubt, themeaning of each term ‘mode(s)’, ‘function(s)’, and ‘system(s)’ isequivalent to the others in this specification. Namely, the meaning of‘mode(s)’ includes and is equivalent to that of ‘function(s)’ and‘system(s)’, the meaning of ‘function(s)’ includes and is equivalent tothat of ‘mode(s)’ and ‘system(s)’, and the meaning of ‘system(s)’includes and is equivalent to that of ‘mode(s)’ and ‘function(s)’.Therefore, even only mode(s) is expressly utilized in thisspecification, it impliedly includes function(s) and/or system(s) by itsdefinition.

Paragraph [0414]—<<Multiple Software Download Function>>

Paragraph [0415]—Paragraph [0416] through Paragraph [0422] illustrate(s)the multiple software download function which enables CommunicationDevice 200 to download a plurality of software programs simultaneously.All software programs, data, any types of information to implement allmodes, functions, and systems described in this specification are storedin a host or server from which Communication Device 200 can download.

Paragraph [0416]—This Paragraph [0416] illustrate(s) the softwareprograms stored in RAM 206 (FIG. 1). As described in Paragraph [0416],RAM 206 includes Multiple Software Download Controller Storage Area20691a. Multiple Software Download Controller Storage Area 20691aincludes Multiple Software Download Controller 20691b, Download SoftwareList Displaying Software 20691c, Download Software Selector 20691d,Download Software Storage Area Selector 20691e, Download Implementer20691f, and Download Repeater 20691g. Multiple Software DownloadController 20691b administers the overall implementation of the presentfunction. One of the major tasks of Multiple Software DownloadController 20691b is to administer and control the timing and sequenceof Download Software List Displaying Software 20691c, Download SoftwareSelector 20691d, Download Software Storage Area Selector 20691e,Download Implementer 20691f, and Download Repeater 20691g. For example,Multiple Software Download Controller 20691b executes them in thefollowing order: Download Software List Displaying Software 20691c,Download Software Selector 20691d, Download Software Storage AreaSelector 20691e, Download Implementer 20691f, and Download Repeater20691g. Download Software List Displaying Software 20691c displays onLCD 201 (FIG. 1) a list of a certain amount or all software programsnecessary to implement the modes, functions, and/or systems explained inthis specification of which the sequence is explained in Paragraph[0417] hereinafter. Download Software Selector 20691d selects one of thesoftware programs displayed on LCD 201 of which the sequence isexplained in Paragraph [0418] hereinafter. Download Software StorageArea Selector 20691e selects the storage area in RAM 206 where thedownloaded software program is stored of which the sequence is explainedin Paragraph [0419] hereinafter. Download Implementer 20691f implementsthe download process of the software program selected by DownloadSoftware Selector 20691d hereinbefore and stores the software program inthe storage area selected by Download Software Storage Area Selector20691e hereinbefore of which the sequence is explained in Paragraph[0420] hereinafter. Download Repeater 20691g executes Multiple SoftwareDownload Controller 20691b which reactivates Download Software ListDisplaying Software 20691c, Download Software Selector 20691d, DownloadSoftware Storage Area Selector 20691e, and Download Implementer 20691fof which the sequence is explained in Paragraph [0420] hereinafter.

Paragraph [0417]—This Paragraph [0417] illustrate(s) the sequence ofDownload Software List Displaying Software 20691c (Paragraph [0416]).Referring to Paragraph [0417], CPU 211 (FIG. 1), under the command ofDownload Software List Displaying Software 20691c, displays a list of acertain amount or all software programs to implement all modes,functions, and systems described in this specification on LCD 201 (FIG.1).

Paragraph [0418]—This Paragraph [0418] illustrate(s) the sequence ofDownload Software Selector 20691d (Paragraph [0416]). Referring toParagraph [0418], the user of Communication Device 200 inputs an inputsignal by utilizing Input Device 210 (FIG. 1) or via voice recognitionsystem identifying one of the software programs displayed on LCD 201(FIG. 1) (S1), and CPU 211, under the command of Download SoftwareSelector 20691d, interprets the input signal and selects thecorresponding software program (S2).

Paragraph [0419]—This Paragraph [0419] illustrate(s) the sequence ofDownload Software Storage Area Selector 20691e (Paragraph [0416]).Referring to Paragraph [0419], CPU 211 (FIG. 1), under the command ofDownload Software Storage Area Selector 20691e, selects a specificstorage area in RAM 206 (FIG. 1) where the downloaded software programis to be stored. The selection of the specific storage area in RAM 206may be done automatically by CPU 211 or manually by the user ofCommunication Device 200 by utilizing Input Device 210 (FIG. 1) or viavoice recognition system.

Paragraph [0420]—This Paragraph [0420] illustrate(s) the sequence ofDownload Implementer 20691f (Paragraph [0416]). Referring to Paragraph[0420], CPU 211 (FIG. 1), under the command of Download Implementer20691f, implements the download process of the software program selectedby Download Software Selector 20691d (Paragraph [0418]) and stores thesoftware program in the storage area selected by Download SoftwareStorage Area Selector 20691e (Paragraph [0419]).

Paragraph [0421]—This Paragraph [0421] illustrate(s) the sequence ofDownload Repeater 20691g (Paragraph [0416]). Referring to Paragraph[0421], the user of Communication Device 200 inputs an input signal byutilizing Input Device 210 (FIG. 1) or via voice recognition system whenthe downloading process of the software program is completed (S1). Ifthe input signal indicates to repeat the process to download anothersoftware program, CPU 211 (FIG. 1), under the command of DownloadRepeater 20691g, executes Multiple Software Download Controller 20691b(Paragraph [0416]), which reactivates Download Software List DisplayingSoftware 20691c (Paragraph [0416]), Download Software Selector 20691d(Paragraph [0416]), Download Software Storage Area Selector 20691e(Paragraph [0416]), and Download Implementer 20691f (Paragraph [0416])to download the second software program while the downloading process ofthe first software program is still in progress by utilizing the methodso-called ‘time sharing’ (S3). Download Software List DisplayingSoftware 20691c, Download Software Selector 20691d, Download SoftwareStorage Area Selector 20691e, and Download Implementer 20691f can berepeatedly executed until all software programs displayed on LCD 201(FIG. 1) are selected and downloaded. The downloading process is notrepeated if the input signal explained in S2 so indicates.

Paragraph [0422]—As another embodiment, as described in this Paragraph[0422], Multiple Software Download Controller 20691b, Download SoftwareList Displaying Software 20691c, Download Software Selector 20691d,Download Software Storage Area Selector 20691e, Download Implementer20691f, and Download Repeater 20691g may be integrated into a singlesoftware program, Multiple Software Download Controller 20691b. First ofall, CPU 211 (FIG. 1) displays a list of all software programsdownloadable from a host or server on LCD 201 (FIG. 1) (S1). The user ofCommunication Device 200 inputs an input signal by utilizing InputDevice 210 (FIG. 1) or via voice recognition system identifying one ofthe software programs displayed on LCD 201 (S2), and CPU 211 interpretsthe input signal and selects the corresponding software program (S3) andselects the storage area in RAM 206 (FIG. 1) where the downloadedsoftware program is to be stored (S4). The selection of the specificstorage area in RAM 206 may be done automatically by CPU 211 or manuallyby the user of Communication Device 200 by utilizing Input Device 210(FIG. 1) or via voice recognition system. CPU 211 then implements thedownload process of the software program selected in S3 and stores thesoftware program in the storage area selected in S4 (S5). The user ofCommunication Device 200 inputs an input signal by utilizing InputDevice 210 or via voice recognition system when the activation ofdownloading process of the software program described in S5 is completed(S6). If the input signal indicates to repeat the process to downloadanother software program, CPU 211 repeats the steps of S1 through S5 todownload the second software program while the downloading process ofthe first software program is still in progress by utilizing the methodso-called ‘time sharing’ (S7). The steps of S1 through S5 can berepeated until all software programs displayed on LCD 201 are selectedand downloaded. The downloading process is not repeated if the inputsignal explained in S6 so indicates.

Paragraph [0423]—For the avoidance of doubt, Paragraph [0416] throughParagraph are also applicable to download data and any types ofinformation other than software programs.

Paragraph [0424]—<<INCORPORATION BY REFERENCE>>

Paragraph [0425]—The following paragraphs and drawings described in U.S.Provisional Application No. 60/521,265, filed 2004-Mar.-23, areincorporated to this application by reference: the preamble described inparagraph [2822] (no drawings); Communication Device 200 (VoiceCommunication Mode) described in paragraphs [2823] through [2828] (FIGS.1 through 2 c); Voice Recognition System described in paragraphs [2829]through [2861] (FIGS. 3 through 19); Positioning System described inparagraphs [2862] through [2893] (FIGS. 20 a through 32 c); Auto BackupSystem described in paragraphs [2894] through [2903] (FIGS. 33 through37); Signal Amplifier described in paragraphs [2904] through [2909](FIG. 38); Audio/Video Data Capturing System described in paragraphs[2910] through [2922] (FIGS. 39 through 44 b); Digital Mirror Function(1) described in paragraphs [2923] through [2931] (FIGS. 44 c through 44e); Caller ID System described in paragraphs [2932] through [2939](FIGS. 45 through 47); Stock Purchasing Function described in paragraphs[2940] through [2949] (FIGS. 48 through 52); Timer Email Functiondescribed in paragraphs [2950] through [2956] (FIGS. 53 a and 53 b);Call Blocking Function described in paragraphs [2957] through [2970](FIGS. 54 through 59); Online Payment Function described in paragraphs[2971] through [2980] (FIGS. 60 through 64); Navigation System describedin paragraphs [2981] through [3003] (FIGS. 65 through 74 a); RemoteControlling System described in paragraphs [3004] through [3022] (FIGS.75 through 85); Auto Emergency Calling System described in paragraphs[3023] through [3031] (FIGS. 86 and 87); Cellular TV Function describedin paragraphs [3032] through [3116] (FIGS. 88 through 135); 3D VideoGame Function described in paragraphs [3117] through [3129] (FIGS. 136through 144); Digital Mirror Function (2) described in paragraphs [3130]through [3139] (FIGS. 145 through 155); Voice Recognition Sys—E-mail (2)described in paragraphs [3140] through [3148] (FIGS. 156 through 160);Positioning System—GPS Search Engine described in paragraphs [3149]through [3191] (FIGS. 161 through 182); Mobile Ignition Key Functiondescribed in paragraphs [3192] through [3214] (FIGS. 183 through 201);Voice Print Authentication System described in paragraphs [3215] through[3225] (FIGS. 202 through 211); Fingerprint Authentication Systemdescribed in paragraphs [3226] through [3238] (FIGS. 212 through 221);Auto Time Adjust Function described in paragraphs [3239] through [3243](FIGS. 222 through 224); Video/Photo Mode described in paragraphs [3244]through [3272] (FIGS. 225 through 242); Call Taxi Function described inparagraphs [3273] through [3313] (FIGS. 243 through 269); Shooting VideoGame Function described in paragraphs [3314] through [3330] (FIGS. 270through 283); Driving Video Game Function described in paragraphs [3331]through (FIGS. 284 through 294); Address Book Updating Functiondescribed in paragraphs through [3365] (FIGS. 295 through 312); BatchAddress Book Updating Function—With Host described in paragraphs [3366]through [3387] (FIGS. 313 through 329); Batch Address Book UpdatingFunction—Peer-To-Peer Connection described in paragraphs [3388] through(FIGS. 329 a through 329 c); Batch Scheduler Updating Function—With Hostdescribed in paragraphs [3393] through [3416] (FIGS. 330 through 350);Batch Scheduler Updating Function—Peer-To-Peer Connection described inparagraphs [3417] through [3421] (FIGS. 351 and 352); CalculatorFunction described in paragraphs [3422] through [3427] (FIGS. 353through 356); Spreadsheet Function described in paragraphs [3428]through [3435] (FIGS. 357 through 360); Word Processing Functiondescribed in paragraphs [3436] through [3451] (FIGS. 361 through 373);TV Remote Controller Function described in paragraphs [3452] through[3474] (FIGS. 374 through 394); CD/PC Inter-communicating Functiondescribed in paragraphs [3475] through (FIGS. 413 through 427); PDWRSound Selecting Function described in paragraphs through [3536] (FIGS.428 through 456); Start Up Software Function described in paragraphs[3537] through [3553] (FIGS. 457 through 466); Another Embodiment OfCommunication Device 200 described in paragraphs [3554] through [3558](FIGS. 467 a through 467 d); Stereo Audio Data Output Function describedin paragraphs [3559] through [3578] (FIGS. 468 through 479); StereoVisual Data Output Function described in paragraphs [3579] through(FIGS. 480 through 491); Multiple Signal Processing Function describedin paragraphs through [3671] (FIGS. 492 through 529); PositioningSystem—Pin-pointing Function described in paragraphs [3672] through[3705] (FIGS. 530 through 553); Artificial Satellite Host described inparagraphs [3706] through [3724] (FIGS. 554 through 567); CCD Bar CodeReader Function described in paragraphs [3725] through [3746] (FIGS. 568through 579); Online Renting Function described in paragraphs [3747]through [3824] (FIGS. 580 through 633); SOS Calling Function describedin paragraphs [3825] through [3845] (FIGS. 634 through 645); InputDevice described in paragraphs [3846] through [3851] (FIGS. 646 through650); PC Remote Controlling Function described in paragraphs [3852]through [3887] (FIGS. 651 through 670); PC Remote Downloading Functiondescribed in paragraphs [3888] through [3937] (FIGS. 671 through 701);Audiovisual Playback Function described in paragraphs [3938] through[3963] (FIGS. 702 through 716); Audio Playback Function described inparagraphs [3964] through [3988] (FIGS. 717 through 731); TicketPurchasing Function described in paragraphs [3989] through [4018] (FIGS.732 through 753); Remote Data Erasing Function described in paragraphs[4019] through [4048] (FIGS. 754 through 774); Business Card Functiondescribed in paragraphs [4049] through [4065] (FIGS. 775 through 783);Game Vibrating Function described in paragraphs [4066] through [4076](FIGS. 784 through 786); Part-time Job Finding Function described inparagraphs through [4097] (FIGS. 787 through 801); Parking Lot FindingFunction described in paragraphs [4098] through [4137] (FIGS. 802through 832); Parts Upgradable Communication Device described inparagraphs [4138] through [4163] (FIGS. 833 a through 833 x); On DemandTV Function described in paragraphs [4164] through [4194] (FIGS. 834through 855); Inter-communicating TV Function described in paragraphs[4195] through [4229] (FIGS. 856 through 882); Display ControllingFunction described in paragraphs [4230] through [4247] (FIGS. 883through 894); Multiple Party Communicating Function described inparagraphs [4248] through (FIGS. 894 a through 917); Display BrightnessControlling Function described in paragraphs [4282] through [4291](FIGS. 918 through 923); Multiple Party Pin-pointing Function describedin paragraphs [4292] through [4339] (FIGS. 924 through 950 f); DigitalCamera Function described in paragraphs [4340] through [4367] (FIGS. 951through 968); Phone Number Linking Function described in paragraphs[4368] through [4391] (FIGS. 968 a through 983); Multiple WindowDisplaying Function described in paragraphs [4392] through [4410] (FIGS.984 through 995); Mouse Pointer Displaying Function described inparagraphs [4411] through [4448] (FIGS. 996 through 1021); House ItemPin-pointing Function described in paragraphs [4449] through [4608](FIGS. 1022 through 1152); Membership Administrating Function describedin paragraphs [4609] through [4651] (FIGS. 1153 through 1188); KeywordSearch Timer Recording Function described in paragraphs [4652] through[4743] (FIGS. 1189 through 1254); Weather Forecast Displaying Functiondescribed in paragraphs [4744] through [4785] (FIGS. 1255 through 1288);Multiple Language Displaying Function described in paragraphs [4786]through [4843] (FIGS. 1289 through 1331); Caller's InformationDisplaying Function described in paragraphs through [4897] (FIGS. 1332through 1375); Communication Device Remote Controlling Function (ByPhone) described in paragraphs [4898] through [4938] (FIGS. 1394 through1415); Communication Device Remote Controlling Function (By Web)described in paragraphs [4939] through [4979] (FIGS. 1416 through 1437);Shortcut Icon Displaying Function described in paragraphs [4980] through[5007] (FIGS. 1438 through 1455); Task Tray Icon Displaying Functiondescribed in paragraphs [5008] through [5030] (FIGS. 1456 through 1470);Multiple Channel Processing Function described in paragraphs [5031]through [5078] (FIGS. 1471 through 1498); Solar Battery ChargingFunction described in paragraphs [5079] through [5092] (FIGS. 1499through 1509); OS Updating Function described in paragraphs [5093]through [5160] (FIGS. 1510 through 1575); Device Managing Functiondescribed in paragraphs [5161] through [5178] (FIGS. 1576 through 1587);Automobile Controlling Function described in paragraphs [5179]through[5227] (FIGS. 1588 through 1627); OCR Function described in paragraphs[5228] through [5263] (FIGS. 1628 through 1652); Real-time GPS Functiondescribed in paragraphs through [5333] (FIGS. 1653 through 1712); CCDVideo Stabilizing Function described in paragraphs [5334] through [5365](FIGS. 1713 through 1736); DVD Remote Controlling Function described inparagraphs [5366] through [5404] (FIGS. 1737 through 1757); Dual FrameBuffer Implementing Function described in paragraphs [5405] through[5421] (FIGS. 1758 through 1767); Mouse Pointer Image Auto ChangingFunction described in paragraphs [5422] through [5435] (FIGS. 1768through 1774); Dual CCD Camera Function described in paragraphs [5436]through [5456] (FIGS. 1775 a through 1786); Radio Tuner Functiondescribed in paragraphs [5457] through [5487] (FIGS. 1787 through 1812);Registered Voice Recognizing Function described in paragraphs [5488]through [5527] (FIGS. 1813 through 1842); Host's TV ResolutionConverting Function described in paragraphs [5528] through [5557] (FIGS.1843 through 1864); Voice Shortcut Recognizing Function described inparagraphs [5558] through [5592] (FIGS. 1865 through 1889); Vital SignMonitoring Function described in paragraphs [5593] through [5682] (FIGS.1890 a through 1954); Attached File Emailing Function described inparagraphs [5683] through [5695] (FIGS. 1955 through 1961); MovieeTicket Function described in paragraphs [5696] through [5748] (FIGS.1962 through 2002); Carrier Prepaid eCard Function described inparagraphs [5749] through [5789] (FIGS. 2003 through 2032); CarrierePass Function described in paragraphs [5790] through [5829] (FIGS. 2033through 2061 b); Communication Device 200 Installed In Carrier describedin paragraphs [5830] through [5831] (FIG. 2062); Wireless CommunicationFacilitating System described in paragraphs [5832] through [5861] (FIGS.2063 through 2076 b); In-Carrier Notifying Function described inparagraphs [5862] through [5892] (FIGS. 2077 through 2093); Station NameNotifying Function described in paragraphs [5893] through [5922] (FIGS.2094 through 2110); Restaurant eMenu Function described in paragraphs[5923] through [5965] (FIGS. 2111 through 2144); Geographic LocationRecording Function described in paragraphs [5966] through [6007] (FIGS.2145 through 2176 b); CCD Dictionary Function described in paragraphs[6008] through [6032] (FIGS. 2177 through 2195 b); Schedule NotifyingFunction described in paragraphs [6033] through [6059] (FIGS. 2196through 2215); Customized Device Purchasing System described inparagraphs [6060] through [6100] (FIGS. 2216 through 2250); MultipleType TV Program Distributing System described in paragraphs [6101]through [6131] (FIGS. 2251 through 2274); Multiple TV Screen DisplayingFunction described in paragraphs [6132] through [6163] (FIGS. 2275through 2297); Touch Panel Function described in paragraphs [6164]through [6189] (FIGS. 2298 through 2315); Communication Device FindingFunction described in paragraphs [6190] through [6201] (FIGS. 2316through 2322); Carrier Safety Measure Controlling Function described inparagraphs [6202] through [6236] (FIGS. 2323 through 2342); ProductInformation Retrieving Function (CCD) described in paragraphs [6237]through [6265] (FIGS. 2343 through 2360); Product Information StoredChip Function described in paragraphs [6266] through [6303] (FIGS. 2361through 2385); Karaoke Playing Function described in paragraphs [6304]through [6332] (FIGS. 2386 through 2406); Performing Pattern IdentifyingAnti-Virus Function described in paragraphs through [6355] (FIGS. 2407through 2421); Continue Enabled Video Game Function described inparagraphs [6356] through [6378] (FIGS. 2422 through 2436); ResumeEnabled Video Game Function described in paragraphs [6379] through[6401] (FIGS. 2437 through 2451); Signal Forwarding Function describedin paragraphs [6402] through [6430] (FIGS. 2452 through 2472);In-Carrier Auto Implementing Mode Function described in paragraphs[6431] through (FIGS. 2473 through 2492); Voice Message DisplayingFunction described in paragraphs through [6481] (FIGS. 2493 through 2503c); Human Toes Displaying Function described in paragraphs [6482]through [6499] (FIGS. 2504 through 2521); Wrinkles/Muscles DisplayingFunction described in paragraphs [6500] through [6541] (FIGS. 2522 athrough 2552 e); Protruded Body Part Displaying Function described inparagraphs [6542] through [6561] (FIGS. 2553 through 2566 b); SatelliteTV Program Displaying Function described in paragraphs [6562] through[6606] (FIGS. 2567 through 2601); Definition of Communication Device 200described in paragraphs [6607] through [6608] (no drawings); MultipleMode Implementing Function described in paragraphs [6610] through [6617](FIGS. 395 through 400); Multiple Software Download Function describedin paragraphs [6618] through [6627] (FIGS. 401 through 407); SelectedSoftware Distributing Function described in paragraphs [6628] through[6647] (FIGS. 1376 through 1393 d); Multiple Software Download And ModeImplementation Function described in paragraphs [6648] through [6655](FIGS. 408 through 412); and the last sentence described in paragraph[6657] (no drawings).

1. A method for a communication device comprising a microphone, aspeaker, an input device, a display, a camera, a touch panel, and awireless communicating system, said method comprising: a functionimplementing step in which a specific function is implemented; whereinsaid communication device implements a voice communicating function, anattached file emailing function, a geographic location function, adictionary function, a schedule notifying function, a multiple type TVprogram function, a multiple TV screen displaying function, a touchpanel function, a communication device finding function, and a resumeenabled video game function, independently or simultaneously; voicecommunication is implemented by utilizing said microphone and saidspeaker, when said voice communicating function is implemented in saidstep; an email is sent with a file attached thereto, when said attachedfile emailing function is implemented in said step; a communicationdevice geographic location which indicates the geographic location ofsaid communication device is indicated on a map displayed on saiddisplay, a corresponding street address which corresponds to saidcommunication device geographic location is displayed on said display,and a corresponding phone number which corresponds to said communicationdevice geographic location or said corresponding street address isdisplayed on said display, when said geographic location function isimplemented in said step; an image is retrieved via said camera of saidcommunication device, an alphanumeric data is retrieved from said image,and an explanation data corresponding to said alphanumeric data isdisplayed on said display, when said dictionary function is implementedin said step; a notice is displayed on said display when a schedule isabout to start, when said schedule notifying function is implemented insaid step; a satellite TV program data is received via said wirelesscommunicating system and output from said speaker and said display undera 1st mode, and a ground wave TV program data is received via saidwireless communicating system and output from said speaker and saiddisplay under a 2nd mode, when said multiple type TV program function isimplemented in said step; a plurality of TV screens are displayed onsaid display, wherein said plurality of TV screens include a 1st celland a 2nd cell, a 1st TV program data and a 2nd TV program data arereceived via said wireless communicating system and said 1st TV programdata of a shrunk version is displayed in said 1st cell and said 2nd TVprogram data of a shrunk version is displayed in said 2nd cellsimultaneously, when said 1st cell is selected by said input device,said 1st TV program data of a non-shrunk version is displayed on saiddisplay, and when said 2nd cell is selected by said input device, said2nd TV program data of a non-shrunk version is displayed on saiddisplay, when said multiple TV screen displaying function is implementedin said step, wherein each of the TV program data of the non-shrunkversion is an image larger in size than the corresponding TV programdata of the shrunk version; said communication device is operated viasaid touch panel, when said touch panel function is implemented in saidstep; when said communication device detects a predetermined audio datavia said microphone, said communication device responds by outputting aresponding sound data, which is a certain sound data, from said speakerin order to assist the user to find the location of said communicationdevice, when said communication device finding function is implementedin said step; and a video game, which is operable to be resumed from thepoint which said video game was paused, is performed when said resumeenabled video game function is implemented in said step.
 2. Acommunication device comprising: a microphone; a speaker; an inputdevice; a display; a camera; a touch panel; a wireless communicatingsystem; a voice communicating means, wherein voice communication isimplemented by utilizing said microphone and said speaker; an attachedfile emailing means, wherein an email is sent with a file attachedthereto; a geographic location means, wherein a communication devicegeographic location which indicates the geographic location of saidcommunication device is indicated on a map displayed on said display, acorresponding street address which corresponds to said communicationdevice geographic location is displayed on said display, and acorresponding phone number which corresponds to said communicationdevice geographic location or said corresponding street address isdisplayed on said display; a dictionary means, wherein an image isretrieved via said camera of said communication device, an alphanumericdata is retrieved from said image, and an explanation data correspondingto said alphanumeric data is displayed on said display; a schedulenotifying means, wherein a notice is displayed on said display when aschedule is about to start; a multiple type TV program means, wherein asatellite TV program data is received via said wireless communicatingsystem and output from said speaker and said display under a 1st mode,and a ground wave TV program data is received via said wirelesscommunicating system and output from said speaker and said display undera 2nd mode; a multiple TV screen displaying means, wherein a pluralityof TV screens are displayed on said display, wherein said plurality ofTV screens include a 1st cell and a 2nd cell, a 1st TV program data anda 2nd TV program data are received via said wireless communicatingsystem and said 1st TV program data of a shrunk version is displayed insaid 1st cell and said 2nd TV program data of a shrunk version isdisplayed in said 2nd cell simultaneously, when said 1st cell isselected by said input device, said 1st TV program data of a non-shrunkversion is displayed on said display, and when said 2nd cell is selectedby said input device, said 2nd TV program data of a non-shrunk versionis displayed on said display, wherein each of the TV program data of thenon-shrunk version is an image larger in size than the corresponding TVprogram data of the shrunk version; a touch panel means, wherein saidcommunication device is operated via said touch panel; a communicationdevice finding means, wherein when said communication device detects apredetermined audio data via said microphone, said communication deviceresponds by outputting a responding sound data, which is a certain sounddata, from said speaker in order to assist the user to find the locationof said communication device; and a resume enabled video game means,wherein a video game, which is operable to be resumed from the pointwhich said video game was paused, is performed.
 3. A communicationdevice comprising: a microphone; a speaker; an input device; a display;a camera; a touch panel; an antenna; a voice communicating implementor,wherein voice communication is implemented by utilizing said microphoneand said speaker; an attached file emailing implementor, wherein anemail is sent with a file attached thereto; a geographic locationimplementor, wherein a communication device geographic location whichindicates the geographic location of said communication device isindicated on a map displayed on said display; a dictionary implementor,wherein an image is retrieved via said camera of said communicationdevice, an alphanumeric data is retrieved from said image, and anexplanation data corresponding to said alphanumeric data is displayed onsaid display; a schedule notifying implementor, wherein a notice isoutput from said communication device when a schedule is about to start;a multiple type TV program implementor, wherein a 1st type TV programdata is received via said antenna and output from said speaker and saiddisplay under a 1st mode, and a 2nd TV program data is received via saidantenna and output from said speaker and said display under a 2nd mode;a multiple TV screen displaying implementor, wherein a 1st TV programdata and a 2nd TV program data are received via said antenna, and said1st TV program data and said 2nd TV program data are displayed on saiddisplay simultaneously; a touch panel implementor, wherein saidcommunication device is operated via said touch panel; a communicationdevice finding implementor, wherein when said communication devicedetects a predetermined audio data via said microphone, saidcommunication device responds by outputting a responding sound data,which is a certain sound data, from said speaker; and a resume enabledvideo game implementor, wherein a video game, which is operable to beresumed from the point which said video game was paused, is performed.